-
Notifications
You must be signed in to change notification settings - Fork 2
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
Infra: Introduce npm/yarn #6
Comments
EthanLin-TWer
added a commit
that referenced
this issue
Mar 18, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 18, 2017
This was referenced Mar 20, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 24, 2017
EthanLin-TWer
added a commit
that referenced
this issue
Mar 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
npm init
npm install -g yarn
yarn.lock
filenpm test
in travis script sectionnode_modules
to.gitignore
filePitfall: use yarn to install dependencies every time after yarn.lock is introduced instead of using npm. Otherwise dependencies can't get resolved correctly by travis calling yarn
The text was updated successfully, but these errors were encountered: