5 ms·

It should. .env.local is a common pattern

• tacker2000 3y ago
  Reminds me of vscode never being able to automatically syntax highight .env.local or similar… or is there some setting im missing?
  • rickstanley 3y ago
    `.env.*` files won't highlight in either VSCode or Neovim, but it works fine with `.*.env`. I guess it's some kind of convention.
    • qntmfred 3y ago
      it's because syntax highlighting rules are applied based on the file extension. as long as .env is the extension, it'll work. if the file ends with .local, vscode has no idea that it's supposed to be a .env file type
      • tacker2000 3y ago
        Yes sure, but since .env.local and .env.prod are so widespread one could make a small filter to also include these types of files, no?
        • Timon3 3y ago
          Especially considering the GitHub .gitignore template for Node only ignores .env.local, not .local.env: https://github.com/github/gitignore/blob/main/Node.gitignore#L76-L80 https://github.com/github/gitignore/blob/main/Node.gitignore...