package.json support

Supporting json based description of package seems pretty important, even support for incompatible version of package.json would be a plus.

And my personal preference would be also adding an option to load package description as a js object (without necessity of placing quotes) and with possibility to define scripts not only as a shell commands, but also as functions to which command line arguments and environment variables are passed.

```
{
name: "chris@entropic.dev/ds",
version: "0.0.0-beta",

scripts: {
test: "node test.js" // classic shell script
compile: function(args, env, shell) {
shell.run("ts " + args[0]);
}
},

dependencies: {
"@iarna/toml": "^2.2.3",
"legacy@entropic.dev/figgy-pudding": "^3.5.1"
}
}
```

Your solution could support all these 3 formats (toml > json > js like)