Sebastian Davids
Sebastian Davids
I have opened [another issue](https://gitlab.alpinelinux.org/alpine/aports/-/issues/17323) upstream.
> they point to well known locations (/usr/lib/jvm/...) where only root may write to. If someone has write access to this location you have way more problems than symlinks. This...
related: #539, #3471, #3508
Ensure `dev.containers.experimentalLockfile` is set to `true` in your VS Code user settings. ```console $ mkdir -p /tmp/test/.devcontainer && cd "$_/.." $ npm init -y >/dev/null $ npm i -Ds [email protected]...
> Ensure `dev.containers.experimentalLockfile` is set to `true` in your VS Code user settings. I guess you forgot 👆 Also check that you do not have `devcontainer-lock.json`, `.devcontainer/devcontainer-lock.json`, or something similar...
`engines` and `engineStrict` might not be the correct fields—they specify the runtime environment of the package and not the runtime for the development of the package … [npm engine-strict](https://docs.npmjs.com/cli/v11/using-npm/config?v=true#engine-strict) [package.json...
> devEngines doesn't have any way to define the actual versions Please read more closely … https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines > The supported keys under the devEngines property are [...] `runtime` [...] optionally...
Related: https://github.com/devcontainers/cli/issues/1008
@gowridurgad Could we please get this reviewed …