Michael Bridgen
Michael Bridgen
If you use jk run ./examples/foo/index.js then the input directory is `./examples/foo`, whereas if you use jk run -m ./examples/foo/index.js then the input directory is `.`. In fact, for everything...
This replaces gometalinter with golangci-lint, which I am told is much better. I have enabled the same linters as before, as well as a couple that also happened to pass...
This would speed it up a bit.
An exploratory RFC suggesting the image and module could be given at the same time, e.g., jk validate -m @jkcfg/kubernetes:0.6.2/validate *.yaml (maybe also for imports?)
`jk transform` and `jk generate` both have a `--stdout` argument, which will print all the objects to stdout. But this balks if the objects have different formats (either because the...
It'd be handy to be able to pipe things into `jk validate` (et al?).
A couple of commands (`jk run` and `jk transform`) let you supply literal JavaScript to run, by interpolating the given code into a module, which is then loaded. A standard...
Instead of making people construct npm scaffolding (package.json, package-lock.json, npm-shrinkwrap.json), as in #232 we could just download things from npm when mentioned in an import. Since we know imports statically,...
It's possible to supply e.g., `./example` as the script path (argument to jk run or generate), and it will resolve if there's an `./example/index.js`. But the default input path will...
When unit testing modules (e.g., mixins), we're using the `node` runtime. Inevitably, we'll want to unit test things that depend on the builtins, i.e., the `std` module. One solution is...