mirror of
https://github.com/vale981/apollo-server
synced 2025-03-05 09:41:40 -05:00
Restore comment from Revert "Test on Node 8 and 10 on Circle CI"
Since f0f75b183e93cc91d31255e7ffd60c1de5d4f16e, it seems important to
restore the reasoning for the usage of `yarn` to avoid confusion in the
future. This comment was originally removed in 301e144d23
.
This reverts the comment from that commit and further improves the clarity.
Ref: https://github.com/apollographql/apollo-server/commit/301e144d#r29319011
This commit is contained in:
parent
ddc589d996
commit
559b21d83a
1 changed files with 8 additions and 3 deletions
|
@ -1,14 +1,19 @@
|
|||
version: 2
|
||||
|
||||
#
|
||||
# Reusable Snippets!
|
||||
#
|
||||
# These are re-used by the various tests below, to avoid repetition.
|
||||
#
|
||||
run_install_desired_npm: &run_install_desired_npm
|
||||
run:
|
||||
name: Install npm@6
|
||||
# we use yarn, since Node 6 does not support the latest npm by default, so
|
||||
# use 5
|
||||
# Due to a bug, npm upgrades from the version of npm that ships with
|
||||
# Node.js 6 (npm v3.10.10) go poorly and generally causes other problems
|
||||
# with the environment. Since yarn is already available here we can just
|
||||
# use that to work-around the issue. It's possible that npm cleanup might
|
||||
# prevent this from being necessary, but this installation can be switched
|
||||
# to use `npm` (rather than `yarn`) once Node 6 is no longer tested below.
|
||||
name: Install npm@5, but with yarn.
|
||||
command: sudo yarn global add npm@5
|
||||
|
||||
# These are the steps used for each version of Node which we're testing
|
||||
|
|
Loading…
Add table
Reference in a new issue