.env file configuring to use properties langauge

[ConnorJennison]

For some reason files named exactly .env are auto-configuring to use the properties language instead of dotenv for syntax highlighting. Making this issue to be able to track this.

[PaulMEdwards]

Same here on version 0.23.0.

I also noticed that other .env.* files are not being detected as dotenv nor Properties type. I had to configure VSCode to apply the dotenv language mode to my .env.* files manually.

[jmevel]

If anybody is passing by here and wondering how to configure it in VS Code.
Add this in your settings file

"files.associations": {
  ".env.*": "dotenv"
},

[motdotla]

Thank you @jmevel.

We're investigating whether we can configure that setting as part of our extension so the user would not have to.

We've configured languages.extensions already in package.json but that does not seem to do the trick in all cases.

Seems VScode extensions have many configuration quirks.

[jmevel]

@motdotla thanks for your answer, yes I imagine it could sometimes be tricky to configure such thing in a VS Code extension. At least this issue has a workaround for now.

Thanks a lot for your work !

[motdotla]

I think 0.27.0 and greater solves this. Working well on my machine. It now sets ".env.*": "dotenv" under files.associations in the user's settings.json