plugin compiles functions that do not use node runtime #198
Comments
|
#197 is my attempt at fixing this. It works when I use it for my case but I may have missed some corner cases. |
NoxHarmonium
pushed a commit
to agiledigital/serverless-plugin-typescript
that referenced
this issue
Feb 9, 2020
- Merge in the changes that vectorjohn made in a parallel PR (filtering functions at the plugin level) - Use lodash's pickBy to simplify some logic - Fix an issue with mixed export syntax (export vs module.exports) - Removed redundant tests Fixes serverless#198
NoxHarmonium
pushed a commit
to agiledigital/serverless-plugin-typescript
that referenced
this issue
Feb 9, 2020
- Merge in the changes that vectorjohn made in a parallel PR (filtering functions at the plugin level) - Use lodash's pickBy to simplify some logic - Fix an issue with mixed export syntax (export vs module.exports) - Removed redundant tests Fixes serverless#198
NoxHarmonium
pushed a commit
to agiledigital/serverless-plugin-typescript
that referenced
this issue
Feb 9, 2020
- Merge in the changes that vectorjohn made in a parallel PR (filtering functions at the plugin level) - Use lodash's pickBy to simplify some logic - Fix an issue with mixed export syntax (export vs module.exports) - Removed redundant tests Fixes serverless#198
|
I need this also! |
|
This is fixed in master (but not in any release yet!). |
|
why is this closed? I'm getting this error when combining node (typescript) and python runtimes I'm getting the following error
I think when specifying packaging individually option we reach this line |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I have a project that uses multiple runtimes (configured individually per function), using this plugin will treat them all as TypeScript and attempt to compile them. This blocks using the plugin in a mixed runtime environment.
The text was updated successfully, but these errors were encountered: