One small point: package-lock should be in the repo, for three reasons.
This is how supply chain attacks can be investigated and prevented
A ci/cd path needs package.lock to do its installs; otherwise if it creates one on the spot it's not testing code as committed, but code as would have been created at any given time, and is subject to library drift
Several code scanners eg snyk treat it as positive signal and rank upwards for it
This PR removes package-lock from .gitignore. A subsequent PR will add an actual package lockfile, so that if you decide you want to do that yourself you can merge this, but if you don't want to be bothered you can just merge both.
Your tooling is excellent
One small point: package-lock should be in the repo, for three reasons.
This PR removes package-lock from .gitignore. A subsequent PR will add an actual package lockfile, so that if you decide you want to do that yourself you can merge this, but if you don't want to be bothered you can just merge both.
Fixes codemirror/lang-example#15 (identical text)