Closed jcbhmr closed 1 year ago
Be warned that without a package-lock.json this workflow WILL FAIL because it uses npm ci
which uses the package-lock.json to install a PINNED version of all deps instead of package.json which uses ranges (ex: 1.x.x can install 1.0.0 or 1.15.6)
I recommend getting some other PR to include package-lock.json (like #2 ) before merging this
Part of #3
This PR would...