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:
Remember that error codes like 1211 are clues, not verdicts. Always inspect the broader log context. With the steps outlined above, you can turn this cryptic rejection into a successful “work” order for your Meteor application.
Rebuild native addons:
meteor npm rebuild A corrupted cache is a leading cause of “rejects work” errors.
# Stop any running Meteor instance meteor reset # This clears your project's .meteor/local folder Then delete the global Meteor package cache (if safe): meteor rejects addon 1211 work
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:
: 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
If you have stumbled upon the cryptic error message "meteor rejects addon 1211 work" , you are likely in the midst of a frustrating debugging session. This error, while rare, is notoriously opaque. It combines references to the Meteor JavaScript framework, a potential addon conflict, a numeric code (1211), and a failure state ("rejects work").