file extensions not working
See original GitHub issuevscode 1.4 win 10 x64
I have this
// Configure file associations to languages (e.g. "*.extension": "html"). These have precedence over the default associations of the languages installed.
"files.associations": {
"*.js?": "javascript",
"*.es": "javascript"
},
"vsicons.useFileAssociations": true,
Actual behaviour: only .js files are “iconized”
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Fix File Extension Errors or Problems - [Detailed Guide]
How to Fix File Extension Problems or Error? · First, click on Start > My Computer > Tools and click the Folder Options...
Read more >How to show File Extensions in Windows 11/10
Open Control Panel > Appearance and Personalization. · Now, click on Folder Options or File Explorer Option, as it is now called ·...
Read more >How to turn on hidden filename extensions in Windows
Solution: · Open File Explorer (open any folder). · Click the View tab. · Select "File name extension" · Optionally, you can enable...
Read more >A Problem with Windows File Extensions
Click on the folder to bring it into focus · Select "Tools" >> "Folder Options" · Select the "View" tab · Uncheck the...
Read more >How to open broken computer files | Popular Science
All kinds of problems could be making that PDF fail to load or video refuse to play. Maybe the file has become corrupted,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please, read the new readme as this has changed to support regular expressions.
You’re right, now only supported extensions will work… . es is not in the list of supported extensions so it won’t be considered.
I’ll try to fix it tonight. Sorry for the inconveniences!