Skip to content
This repository was archived by the owner on Jun 21, 2022. It is now read-only.

Conversation

@darkwing
Copy link
Contributor

First step toward upgrade. To test:

  1. Install nvm and use node v 0.10.36
  2. npm rebuild
  3. ./node_modules/.bin/nodeunit tests

What concerns me is needing to npm rebuild instead of just npm install which travis does. memcached is the culprit.

@darkwing darkwing force-pushed the 1189118-kumascript-upgrade branch 4 times, most recently from a5e7fd5 to 025067f Compare September 1, 2015 01:02
bug 1189118 - Add me to contributors list

bug 1189118 - Add build files

bug 1189118 - Specify correct node versions in docs and travis; add updated build files.
@darkwing
Copy link
Contributor Author

darkwing commented Sep 1, 2015

Oddly enough, if I rm -rf node_modules/, then do npm install, everything installs fine. :/

@darkwing
Copy link
Contributor Author

darkwing commented Sep 1, 2015

Important update is making travis run npm rebuild instead of just install. This is important when making updates that contain binaries.

@groovecoder
Copy link
Contributor

Nice update.

@darkwing
Copy link
Contributor Author

darkwing commented Sep 4, 2015

Now that I know we use RPM on stage and prod, I'll want to rethink the rebuild part of travis; could lead to problem :/

@darkwing
Copy link
Contributor Author

darkwing commented Sep 8, 2015

To Do:

  • Add memcached to the git-ignore
  • Change travis back to .travis.yml

@escattone
Copy link
Contributor

This is superseded by PR 69 (#69).

@escattone escattone closed this Dec 14, 2016
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.

3 participants