Allow more options for meta config format/name

That is, to allow not just .meta as a config file, but also .meta.json, .meta.yaml, meta property in package.json, etc.

[mateodelnorte]

For syntax highlighting, just click the change language mode button on the bottom right:

or CMD+Shift+P and select change language mode:

There are plenty of other projects that have non-json and non-js extensions, causing them to not have highlighting. This is not a big deal. If you want highlighting for .meta files, a better idea would be to start a meta VS Code extension. We could put some really powerful commands into it, and it would cover your highlighting.

I don’t see a benefit to unifying with other tooling. You’re creating a new repo for your meta repo. You don’t have to have a package.json in your meta repo. You only would if you want to locally install plugins. And I don’t see a reason to shove all your child project repo locations into your package.json.

Shoving many things into fewer files === more merge conflicts. Separate, and simple is better.

[panoply]

FYI: You can also set file associations in vscode, eg:

{  
 "files.associations": {
    ".meta": "json"
  }
}