-
Notifications
You must be signed in to change notification settings - Fork 20
Should babel-register be a dev-dependency instead of dependency? #654
Comments
Thanks for reporting this! Indeed, we're using I'm not sure which node version Meteor uses these days and which versions we still need to support. Given that the lowest supported node version is advanced enough we might be able to get rid of babel completely in the future. |
🎉 This issue has been resolved in version 4.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Can you try installing |
Ah, no. There's still a bit of code dependent on the |
Remove babel and convert code to use CommonJS format. Convert rules to updated format (https://eslint.org/docs/developer-guide/working-with-rules). closes #654
Remove babel and convert code to use CommonJS format. Convert rules to updated format (https://eslint.org/docs/developer-guide/working-with-rules). BREAKING CHANGE: Changes exported, recommended eslint config (`extends: ["plugin:meteor/recommended"]`) to enable ecmaVersion 6, sourceType module and jsx for the ESLint parser. closes #654
Remove babel and convert code to use CommonJS format. Convert rules to updated format (https://eslint.org/docs/developer-guide/working-with-rules). BREAKING CHANGE: Changes exported, recommended eslint config (`extends: ["plugin:meteor/recommended"]`) to enable ecmaVersion 6, sourceType module and jsx for the ESLint parser. closes #654
🎉 This issue has been resolved in version 5.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I completely removed Note: |
Works great @dferber90, Cheers! |
Hi,
Just noticed after updating meteor to 1.7-rc.3, which uses the new babel runtime package (
@babel/runtime@^7.0.0-beta.46
), thateslint-plugin-meteor
was still depending onbabel-register
/babel-runtime
@6.26
Compared with other plugins, I'm guessing that
babel-register
shouldn't be underdependencies
, but belongs underdevDependencies
instead.eg. https://github.com/3stack-software/eslint-plugin-meteor/commit/dd53fe1bbe9b14e10adfcaafe39af0d36e51c8f4
The text was updated successfully, but these errors were encountered: