Closed uwefassnacht closed 8 years ago
Yes, the issue is because of the rimraf already being present in the local node_modules and pushed. rimraf
functionality differs based on the OS. So as the Bluemix and the local env are different it will have an issue.
So the solution of this is to include node_modules in your .cfignore or use the latest version of ibmiotf
where rimraf
is not used.
Thanks!!
So the solution of this is to include node_modules in your .cfignore
Yes understood (and this is what I did).
or use the latest version of ibmiotf where rimraf is not used.
Great. That fixes the issue. Thanks!
Got the following error when pushing an app with the ibmiotf npm module up to Bluemix. Discussed with @bryancboyd and probably due to node_modules/ being pushed from my local directory (with rimraf already downloaded).
-----> Downloaded app package (27M) -----> Downloaded app buildpack cache (6.6M)
-----> IBM SDK for Node.js Buildpack v2.8-20151209-1403 Based on Cloud Foundry Node.js Buildpack v1.5.0 -----> Creating runtime environment NPM_CONFIG_LOGLEVEL=error NPM_CONFIG_PRODUCTION=true NODE_MODULES_CACHE=true -----> Installing binaries engines.node (package.json): unspecified engines.npm (package.json): unspecified (use default) Resolving node version (latest stable) via 'node-version-resolver' Installing IBM SDK for Node.js (0.12.9) from cache Using default npm version: 2.14.9 -----> Restoring cache Loading 1 from cacheDirectories (default):