Dimitris "Jimi" Charalampidis

> The only thing it does is force contributors and workflows to use Node.js 16 or greater. This. It's vital.

`wpil` workflow is not vital. As much as your OCD (and mine) wants to resolve this, just let it be for now.

I have similar opinion with @robertohuertasm on this. Upcoming September, hopefully, where we will update the minimum `vscode` and `node` versions, you will get your wish.

https://github.com/vscode-icons/vscode-icons/pull/3432#issuecomment-1952779240

@vscode-icons/development This makes total sense to me, since `JSX` and `TSX` is being used outside `React` itself. What we can do, to keep backwards compatibility, is to include this into...

Nothing to be fixed. Pls read again https://github.com/vscode-icons/vscode-icons/wiki/Custom Hint: You are trying to customize `scripts` by altering the default folder icon.

Let me get this clear. You want the default folder icon to be shown for a folder named `scripts`, right?

What you are trying to do is to *customize* your `scripts` folder, thus you fall into the [`customization`](https://github.com/vscode-icons/vscode-icons/wiki/Custom) feature. The way you are trying to use the feature is not...

1. `Custom Icons` is a sub subject of `Fine tuning` which is a sub subject of `Customization`. `Customization` page doesn't provide much info, does it? I was merely pointing you...

Once again we had to do the searching. `mcmeta`: https://minecraft.gamepedia.com/Tutorials/Creating_a_resource_pack#Creating_an_MCMETA_file, https://marketplace.visualstudio.com/items?itemName=xTeal.mcmeta `mcfunction`: https://marketplace.visualstudio.com/items?itemName=arcensoth.language-mcfunction