Skip to content
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

chore: make Travis use Node v11 (1.x) (#1237) #1239

Closed
wants to merge 4 commits into from
Closed

Conversation

wincent
Copy link
Contributor

@wincent wincent commented Apr 24, 2019

We needed to force the use of v11 on the master branch (see #1238) because v12 was causing CI builds to blow up. This is not a problem on the 1.x branch because we were still using v8. But we should use the same version on both branches for consistency.

Related: #1237

We needed to force the use of v11 on the master branch (see #1238)
because v12 was causing CI builds to blow up. This is not a problem on
the 1.x branch because we were still using v8. But we should use the
same version on both branches for consistency.

Related: #1237
I just noticed that we have both a package-lock.json and a yarn.lock on
this branch.

- yarn.lock was added in 176cfd4 (Jan 2017) and only updated once, in
  c59af29 (also in Jan 2017).
- package-lock.json was added in e636edf (Oct 2017) and updated on a
  number of occasions, the latest being in 2cb99ed (April 2019).

Let's standardize on Yarn, to match what we're doing in the "master"
branch and in other projects.
Because we need to move to a newer node-sass in order to build
successfully with Node v11.
@wincent
Copy link
Contributor Author

wincent commented Apr 24, 2019

Ugh... dropping this as not worth the hassle. Old version of gulp with old version of gulp-sass, which means old version of node-sass. Tried to use "natives@1.1.3" (and "natives@1.1.6") to solve build issues, but build is horribly broken and would probably require a bunch of other updates to make it work. Will address the duplicate lock files in a separate pull.

@wincent wincent closed this Apr 24, 2019
@wincent
Copy link
Contributor Author

wincent commented Apr 24, 2019

Superseded by: #1242

@wincent wincent deleted the wincent/1.x/node-11 branch April 24, 2019 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant