-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to node 4.x LTS for addons-linter integration. #2588
Comments
Let's cc @jasonthomas on this so he can start working on packaging up node 4.x for our servers. Should we open a bugzilla ticket separately for this? |
Yeah you'll want an ops bug in bugzilla for that. |
Does the linter theoretically work on 4.x already or is there more work needed? |
We are mirroring nodesource node 4.x already, https://github.com/mozilla-services/puppet-config/blob/0f92cc8a9d1ca3f635908f7d36f89c14df5a20a9/common/modules/yum/manifests/repos/nodesource_4x.pp |
I don't have access to that repo but that's awesome then. Since I can't see the link, can you give me the correct mirror? Our current mirror is:
Same mirror but only |
Yes, replacing 0.12 with 4.x should work. |
Supports mozilla/addons-linter#62 |
added https://bugzilla.mozilla.org/show_bug.cgi?id=1254553 to upgrade nodejs on dev, stage and prod |
Upgrade to nodejs 4.x, fixes #1799
Since we're looking to use node 4.x and above for the addons-frontend it might make sense to update the node version we're proposing to use for the linter.
/cc @EnTeQuAk
The text was updated successfully, but these errors were encountered: