-
Notifications
You must be signed in to change notification settings - Fork 90
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
Please ignore devDependencies in deploynodeapp #31
Comments
Fixing this requires a change to Apigee Edge, because that's where NPM runs when apigeetool asks it to. I opened issue APIRT-2452 to track the resolution of this within Apigee. |
Thanks for opening this issue within Apigee. Please let us know if/when it's resolved. |
@gbrail any updates here? |
I've got someone looking at this and will update when we know something. |
We have a PR inflight on Apigee Edge for the necessary API changes, to make We will update this issue when the fixes are merged and released. |
We are still waiting on API changes to release. When those changes are released, we will cut a new release of |
I can't deploy on Apigee with my
package.json
"as is" with the-R
option because the devDependencies that I use (e.g., gulp, etc.) are too large and exceeds the Proxy Bundle limit. As a workaround, I have to do the following:npm install --production
-U
optionBut this is still a defect. Please fix your deployment tool to use
npm install --production
. That way, you're just pulling in thedependencies
frompackage.json
, and everything works as expected.The text was updated successfully, but these errors were encountered: