All the .eslintrc, .eslintignore and other files can add some cognitive load to folks getting started creating JupyterLab extensions, and might make them feel overwhelmed.
Proposed Solution
It's possible to place the config in the package.json directly.
Similar to pyproject.toml holding the config for some Python tools.
Maybe we can do the same in the cookiecutter by default to avoid having too many files.
Problem
All the
.eslintrc
,.eslintignore
and other files can add some cognitive load to folks getting started creating JupyterLab extensions, and might make them feel overwhelmed.Proposed Solution
It's possible to place the config in the
package.json
directly.Similar to
pyproject.toml
holding the config for some Python tools.Maybe we can do the same in the cookiecutter by default to avoid having too many files.
Additional context
Example PR implementing that: https://github.com/jupyter-server/jupyter-resource-usage/pull/188