-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
Specifying a path to the package.json #80
Comments
Hi @jayair . thank you for the issue |
I'm using a monorepo with a single root package.json and have hit the same issue. My preference would be for the default behaviour to be to climb up directories until it finds a package.json file like the serverless-webpack plugin does without requiring an explicit configuration setting. |
🎉 This issue has been resolved in version 1.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@jayair @paulswail hey guys, I added an optional |
@floydspace That's awesome. Thanks for quick response. I'll give it a test shortly. And we'll be promoting this plugin ASAP. |
Hi there,
I was testing this plugin out and ran into some issue. We have a monorepo setup where the individual services do not have their own
package.json
. I noticed that this plugin uses the code from serverless-webpack. Any plans to add the ability to set your own path for thepackage.json
? Or alternatively, climbing up the directories to look for apackage.json
file?https://github.com/serverless-heaven/serverless-webpack/blob/31662103851933ac277b02119912b593c2914ece/lib/packExternalModules.js#L242 => https://github.com/floydspace/serverless-esbuild/blob/master/src/packExternalModules.ts#L151
The text was updated successfully, but these errors were encountered: