Max Howell
Max Howell
I feel `package.json` *is* generic. Node doesn’t own it. Right now it does mean `node` but it doesn’t have to—tools like ours choosing it can effect that. It is literally...
Part of the reason I picked README and `package.json` is in my experience the people who make choices about what tools to use are far more apposed to adding “yet...
I guess really it should be `package.yml` and use the same format as the pantry. We have a messy story currently with all this stuff TBH.
> immediately my editor started thinking it was a node.js project this is a pretty good reason to not standardize on it. I don't wish to fight with existing tooling,...
Hey all, sorry I was absent from this thread. I have been thinking on it for the past month or so. My attitude that “the README is where this should...
We now support `tea.yml` or `tea.yaml` in addition to YAML front matter supplementing all files that dev tools support.
The format is the same as for YAML front matter, in that: ``` dependencies: nodes.org: ^16 env: FOO: BAR version: 1.2.3 ``` Are supported keys. Our “dev env” system picks...
I've come round to this provided we use `package.yml` thus we are being consistent with our longer term goals.
`tea.yml` or `tea.yaml` support officially dropped in 0.23.
Yes sorry to be confusing. I meant it went live. We will be keeping this feature forever!