Domantas Petrauskas

Probably the best solution is adding a new sbt setting that would allow passing these variables to underlying npm commands. Should be easily doable.

You can achieve this now with `yarnExtraArgs` setting, they will get passed to `yarn install`. Implementation of https://github.com/scalacenter/scalajs-bundler/issues/417 will make this capability somewhat more expressive.

This PR to be specific - https://github.com/scalacenter/scalajs-bundler/pull/420.

Ah, now I understand the issue. All package managers that I know of (`npm`, `yarn`, `pnpm`) have some means to achieve this. I suppose a setting for `frozenLockfile: Boolean` would...

No worries, makes sense to have this feature anyways. What replacements do you have in mind? Mind sharing some issues/PRs you are working on? I would be interested in checking...

Related to https://github.com/scalacenter/scalajs-bundler/issues/423.

@evbo I ran into the same issue and simply published the module explicitly, same as the CI workflow does it - https://github.com/scalacenter/scalajs-bundler/blob/main/.github/workflows/release.yml#L21-L22. Adding the project to aggregate makes sense to...

@sjrd Can we merge this?

@sjrd I made changes for which I did not have further questions, please review the discussions and the code when you can.

When suggesting this I mainly had interactions with Webpack in mind: - https://github.com/scalacenter/scalajs-bundler/blob/d083e6df3fe2ac795ae16ba69696039bf85f85a3/sbt-scalajs-bundler/src/main/scala/scalajsbundler/Webpack.scala#L285 - https://github.com/scalacenter/scalajs-bundler/blob/d083e6df3fe2ac795ae16ba69696039bf85f85a3/sbt-scalajs-bundler/src/main/scala/scalajsbundler/WebpackDevServer.scala#L54 It is not possible to intercept node executable used for them.