-
Notifications
You must be signed in to change notification settings - Fork 1.3k
NPM error when try to build dev environment #550
Comments
I'm having the same issue on Ubuntu 14 with the current code, and previous code. |
@wisco24 Do you remember the last build that was working? |
I think it has to do with a new version of a dependency. |
There is a PR almost complete, just doing some final testing. |
@stevcoll If you want us to test the PR, let us know \o/ |
@stevcoll same as Ayrton, let me know if I can help with anything or testing, I need to run a deploy tonight so this is going to help a lot! thanks. |
I banged my head on this one for a bit. Seems like a dependency issue in the provision.sh script. I commented out
and added
Nodejs will install npm as well. Seemed to fix the issue. |
@ayr-ton / @wisco24 / @juanrossi / All: The update to fix this issue has been submitted as a PR against Branch: https://github.com/WraySec/fbctf/tree/bug_fixes / Commit: WraySec/fbctf@fae49641b9661f0ec4081848655604de7e0f89a4 Thank you for looking into this, your fix is fairly close the fix that we implemented. The only differences are keeping the initial npm install and purging the legacy package before updating to the newest version. |
Thanks everyone. @justinwray I think to prevent this type of issues in the future it would be best to install specific versions con npm modules, nodejs, etc. It requires a little more work to test and update versions, but it would help. |
Maybe switch to using Yarn? https://yarnpkg.com/lang/en/docs/yarn-lock/ (like npm-shrinkwrap but reproducible) |
@ayr-ton @juanrossi Could one of you test the changes on Vagrant if you get a chance? Having some issues with my environment here. |
@stevcoll I'll try to test it locally. I'm using Docker and the fix worked perfectly. |
@juanrossi Great! I tested it on all other provision modes except for manual separate servers, which should be fine since the services are just broken out. |
* Remove NodeJS-Legacy (Fixes: #550) * Updated version of node.js installed to fix critical provisioning errors. By default, Ubuntu 14.04 uses a legacy version of node.js. This code removes the legacy version and updates to a newer version. * Source: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions * This PR fixes the provision/build issue from #550
…ixes: #554) (#555) * Downgraded Dropkick.js to version 2.1.10. The project originally was built using 2.1.10 and specified a near version in the 2.x.x release family. On August 27th 2017 Dropkick.js released version 2.2.0 which is incompatible with ES6 specs. The incompatibility with the new release of Dropkick.js caused the provisioning of the platform to fail. * Moved the installation process for Node.js to a function within `lib.sh`. This change streamlines the provision script. * Removed the installation of `wget` from provisioning. `wget` is no longer used within the project and is therefore unneeded. * Updated the `dl()` download function within the provision script to use `curl` exclusively, with retry options. The retry options are set to 5 retries with a 15-second delay between retries. The addition of the retry option ensures the provision can continue if there is a temporary issue with a remote connection or availability of a remote resource. * Added the `dl_pipe()` download function to the provision script. This download function provided the data from the remote resource via standard output to be piped into another command. As piping downloads within the provisioning process have become more common, this function streamlines the process. * Fixes #554 * Updates fixes for #550
Confirmed that the last two PRs has fixed the issue. |
* Remove NodeJS-Legacy (Fixes: #550) * Updated version of node.js installed to fix critical provisioning errors. By default, Ubuntu 14.04 uses a legacy version of node.js. This code removes the legacy version and updates to a newer version. * Source: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions * This PR fixes the provision/build issue from #550
…ixes: #554) (#555) * Downgraded Dropkick.js to version 2.1.10. The project originally was built using 2.1.10 and specified a near version in the 2.x.x release family. On August 27th 2017 Dropkick.js released version 2.2.0 which is incompatible with ES6 specs. The incompatibility with the new release of Dropkick.js caused the provisioning of the platform to fail. * Moved the installation process for Node.js to a function within `lib.sh`. This change streamlines the provision script. * Removed the installation of `wget` from provisioning. `wget` is no longer used within the project and is therefore unneeded. * Updated the `dl()` download function within the provision script to use `curl` exclusively, with retry options. The retry options are set to 5 retries with a 15-second delay between retries. The addition of the retry option ensures the provision can continue if there is a temporary issue with a remote connection or availability of a remote resource. * Added the `dl_pipe()` download function to the provision script. This download function provided the data from the remote resource via standard output to be piped into another command. As piping downloads within the provisioning process have become more common, this function streamlines the process. * Fixes #554 * Updates fixes for #550
HEAD version 3047351
It is happening both with the manual, vagrant and docker builds.
Following the default steps on README, using Mac OS Sierra as the development machine, I got the following NPM error:
The text was updated successfully, but these errors were encountered: