GUI for package.json
PROJECT NOT YET FUNCTIONAL.
- Allow editing of
package.json
- Allow overwriting existing
- Adding new properties
- Delete existing
- Ensure non-recognized fields can be edited as JSON
Some wishes, but not necessarily with plans to follow-through!
- Be sure to update project description in README and our
package.json
if we expand the scope - Keep stand-alone but also make plug-in for Atom (with handler for
package.json
type?). - Integrate npm-gui for dependencies.
- Integrate npm-scripts-gui for scripts execution.
- Save pipelines of dependencies, scripts for reuse across projects (e.g., adding ESLint dependencies and "eslint" script, for Rollup, etc.)
- Pull-down to switch between
package.json
of other open repos in Atom. - JSON-Schema-driven ESLint (and options) editing (npmpathy desired to function not only for npm, but related).
- Add license-checker
- Make a pseudo-standard field (under
directories
?) forchanges
to point to aCHANGES.md
file (and check common names listed at https://docs.npmjs.com/files/package.json#files). - Parse
browserslist
to display browser icons