Christopher Hiller
Christopher Hiller
This would check a `.d.ts` file (the file pointed to by the `types` field in `package.json` or the `types` conditional export(s)) to make sure passes strict mode checks. I don't...
Assert that if there's an `engines` field in a `package.json` (probably only the `node` one for now), _and_ something like `exports` is provided (without a fallback to `main`), and the...
This rule would check that--unless specified in the `os` field of `package.json`--the package is not portable as installed. This would include things like: - bash-isms, path expansion or shell scripts...
This rule would determine the package type (ESM or CJS) via `package.json`, then check all the sources within to assert they are using the proper extensions. e.g: ```ts const isESM...
Right now, `midnight-smoker` assumes terminal emoji support. Find a graceful fallback and apply it.
With the addition of support for multiple package managers, we lost the ability to pass extra arguments into the "pack", "install", and "run scripts" steps. While this may be too...
If we get a 127, it means an executable could not be found. A common cause of this is failing to provide the `--add` option. Detect this (ideally in a...
This would be useful combined with the package manager support in #273. Instead of pack/install/run, we'd just run the scripts against the package managers. This would further enable the "package...
You have two branches, `master` and `foo`. Both have the `gh-pages` task defined, but `foo`'s is incorrect for whatever reason. You run `gh-pages` while in `foo`. Whoops! The wrong files...
### What version of `starlight` are you using? 0.15.1 ### What version of `astro` are you using? 4.0.8 ### What package manager are you using? npm ### What operating system...