Skip to content

Conversation

@rajivshah3
Copy link

Temporarily downgrades NodeJS because a nested dependency (bundlesize@0.17.1 > brotli-size@0.0.1 > iltorb@1.3.10) does not support Node 12. This can probably be reverted once siddharthkp/bundlesize#299 is merged. Alternatively, a package-lock.json or npm-shrinkwrap.json can be used to upgrade brotli-size to 0.1.0.

@rajivshah3 rajivshah3 changed the title Use Node 11 on CI Using Node 11 on CI May 9, 2019
NicoZelaya
NicoZelaya previously approved these changes May 15, 2019
@NicoZelaya
Copy link

It does seem like quite a harmless change, especially since there is a PR on bundlesize to fix it.

@@ -1,6 +1,6 @@
language: node_js
node_js:
- node
Copy link
Member

@emilyemorehouse emilyemorehouse May 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason why we can't use 12? Or is 12 explicitly what is breaking this?

I'd like to stay on LTS since the end of life for 11 is quite soon (2019-06-01)

EDIT: sorry, hastily read this! let me look into this, as I am still hesitant to move to 11.

Copy link
Author

@rajivshah3 rajivshah3 May 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emilyemorehouse it can be reverted once the downstream issue is fixed. Another option would be to use a package-lock or npm-shrinkwrap to upgrade brotli-size

If staying on an LTS release is a priority, I think 10 would work as well and will be supported until April 2021

Copy link

@mapleeit mapleeit May 21, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve of using node 10 for now.

There are several packages still can not used with node 12. And we should keep the CI working at least. Otherwise contributors will be confused.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to 10 in 0430711, looks like CI is still working

@rajivshah3 rajivshah3 changed the title Using Node 11 on CI Using Node 10 on CI May 21, 2019
@peter-mouland
Copy link

peter-mouland commented May 30, 2019

anything willing contributors can do to help get this merged in?

I think you're going to see a tonne of noise because of email that GitHub sent out: #2183
#1485

@pi0
Copy link

pi0 commented May 30, 2019

at least 1,327,670 emails are already sending 😄 Thanks @github :)

@AAllport
Copy link

AAllport commented May 30, 2019

Anything willing contributors can do to help get this merged in?

What's blocking this merge?

@pi0
Copy link

pi0 commented May 30, 2019

@AAllport I think nothing but time. I understand the essence of next axios release and this is really annoying for GitHub notification. But let's not to forget this is an opensource project. OSS maintainers, even by doing best efforts can't always dedicate full time on the project.

@rajivshah3
Copy link
Author

Sorry to ping again @emilyemorehouse . It looks like GitHub is now sending emails to everyone that uses axios. Would you be able to review this PR when you get a chance?

@emilyemorehouse
Copy link
Member

CI is passing as-is now (and a release has been made). Can this be closed?

@rajivshah3
Copy link
Author

Ah ok, if it's passing now then this isn't necessary

@rajivshah3 rajivshah3 closed this May 30, 2019
@rajivshah3 rajivshah3 deleted the fix/ci branch May 30, 2019 16:33
@axios axios locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants