How to Build Legacy Version for NPM Package Dependency in Meteor Package

As I understand it, Atmosphere packages can’t treat Npm.depends dependencies as modern modules, so they won’t be understood or processed that way.

This is another reason to move Atmosphere packages to local NPM packages instead. Atmosphere has long-standing limits and few recent changes, aside from bundle size work in 3.4. Standard NPM packages avoid those limits and prepare you for the future.

So, is there anything in your package code setup blocking to move to a NPM package instead of an Atmosphere one? I’d only use Atmosphere when you need to hook the bundler or Meteor runtime lifecycle in a specific way, or you can be 100% compatibility. For incompatibilities or in general, I’d shift them to NPM packages so the code lives in your app and you can handle it with recompile or rspack’s compileWithRspack helper.

Feel free to open a Meteor tracker issue for future support. I’d still prioritize moving to standard, easy-to-integrate NPM packages.