METEOR_VERBOSE=1 meteor run # or on Windows: set METEOR_VERBOSE=1 && meteor run Look for lines containing 1211 , addon , or reject . Note the file path and the exact preceding line. This will tell you whether the error comes from Node.js, Meteor’s build plugin system, or the operating system. Native addons are version-sensitive. Run:
Rebuild native addons:
meteor npm rebuild A corrupted cache is a leading cause of “rejects work” errors.
: Run meteor reset && meteor npm install && meteor run with verbose logging, and apply the relevant fix from the steps above. Your development server should start smoothly.
meteor list --details Look for any package with a version or ID containing 1211 . If none, search your .meteor/packages file for custom local addons. If you suspect a specific npm package (e.g., node_modules/some-native-addon ), temporarily remove it:
rm -rf ~/.meteor/package-metadata # On Windows: rmdir /s %USERPROFILE%\.meteor\package-metadata Try to identify which package or addon corresponds to ID 1211. Run: