-
-
Notifications
You must be signed in to change notification settings - Fork 793
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
Cannot run both Node and Python offline runtimes simultaneously #993
Comments
Running into this same exact issue. Did you ever find a solution to this? |
We did not. We ended up only using Python lambdas for this project =\ |
The problem is that the webpack output directory is prefixed with a period To fix, have webpack output everything to a directory without the output: {
libraryTarget: 'commonjs',
path: path.join(__dirname, 'dist'),
filename: '[name].js',
}, |
Our project doesn't have NodeJS, but we also ran into this error, at the same line: module = import_module(args.handler_path.replace(os.sep, '.')) We managed to fork |
I get the error even though on deploy my code works. I can deploy my zip file using sls deploy and can hit the endpoint without error. Locally, using edit: It would be great if we could provide an artifact to |
Bug Report
Current Behavior
Running serverless offline with both Node and Python runtimes gives the following error when hitting a Python endpoint:
Sample Code
Expected behavior/code
Expecting to run both TypeScript and Python lambdas offline simultaneously.
Environment
serverless
version: 1.71.3serverless-offline
version: 6.2.0node.js
version: 12.6.2OS
: macOS 10.14.6optional, if you are using any of the following frameworks to invoke handlers
python
version: 3.6Additional context/Screenshots
When I run
serverless offline
, I am able to successfully go to the health endpoint (javascript), but going to the health-py endpoint gives me the error pasted above.If I instead run
serverless offline --location .
, I am able to successfully go to the health-py endpoint, but the health endpoint gives me this errorThe text was updated successfully, but these errors were encountered: