ssoper,

question for other #nodejs #javascript devs out there. is there a way to get the predictability of reproducible versioning between dev and deployed without having to lock down your package.json to exact versions? concern is that locking down versions now introduces a quarterly upgrade cycle that sucks up dev time. i'm also not a fan of dependabot's yarn.lock only updates.

this whole convo started w/ #nextjs 13.3.1 release with a nasty bug.

assaf,
@assaf@mas.to avatar

@ssoper you can use override/resolutions to lock specific packages from being upgraded

ssoper,

@assaf that’s something we’re considering, locking core dependencies and letting others float, thank you for the suggestion

  • All
  • Subscribed
  • Moderated
  • Favorites
  • programming
  • DreamBathrooms
  • ngwrru68w68
  • modclub
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • mdbf
  • GTA5RPClips
  • provamag3
  • tacticalgear
  • tester
  • normalnudes
  • osvaldo12
  • everett
  • cubers
  • ethstaker
  • Leos
  • megavids
  • cisconetworking
  • anitta
  • JUstTest
  • lostlight
  • All magazines