Add first-class support for frozen lockfiles

[armanbilge]

Add first-class support for frozen lockfiles

[ptrdom]

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 be ideal, defined outside of package manager. Then each package manager should alter its commands to respect it. I would not want to assume what should be the default behavior, package managers themselves are moving towards locking by default. scalajs-bunder is not v1 so we can break things at will 😅 Definitely doable. What do you think? I could work on it.

[ptrdom]

You can achieve this now with yarnExtraArgs setting, they will get passed to yarn install. Implementation of #417 will make this capability somewhat more expressive.

[ptrdom]

This PR to be specific - #420.

[armanbilge]

Right, this issue is about adding "first-class" support for frozen lockfiles, precisely so you don't have to muck about with yarnExtraArgs. IMHO this is important enough to surface directly to the API. See for example the linked issue about Scala Steward integration.

[armanbilge]

Yes, exactly :) sure, that would be great. However, personally I've become disillusioned about scalajs-bundler and using npm dependencies from Scala.js libs in general (I've focused on replacing them with pure Scala libs instead) so atm I no longer have much interest in this, sorry :(

[ptrdom]

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 them out.

[armanbilge]

Here's a few off the top of my head, but if there's something specific you are curious about I can point you in the right direction.

• typelevel/skunk#587
• http4s/http4s#6009
• https://github.com/buntec/scala-js-snabbdom
• scala-js/scala-js-js-envs#20 (comment)