-
Notifications
You must be signed in to change notification settings - Fork 114
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
Incompatibility with serverless-plugin-typescript #85
Comments
The error seems to be related to TypeScript. It can happen if you have an invalid tsconfig.app.json or tsconfig.json or if you have invalid code like a getter without a return. This might also be caused because plugins:
- serverless-plugin-typescript
- serverless-plugin-warmup |
Any progress on this? |
@juanjoDiaz I am experiencing the same issue and put yml plugins in order you specified but does not work. |
Same here. Order of plugins does not seem to help |
I am able to use serverless-plugin-typescript without issue: Here is my tsconfig:
Here is the relevant portion of my
|
Thank you for suggested fixes. I haven't had a chance to revisit this in our code. We implemented a work around which has to be removed to test this. If anyone else can verify this fix works please close this issue. It will be a while before we have any resources to verify. |
I'll close this for now. It seems clear that the problem is in serverless-plugin-typescript (which seems to be abandoned, so serverless-webpack might be a better option) and there seems to be a workaround. Feel free to reopen if there is anything else. |
@juanjoDiaz sorry to drag this up - Serverless-Plugin-Typescript is under active dev at the moment, can we reopen this? |
Is there anything that we can do here, @claridgicus? The problem, as stated in serverless/serverless-plugin-typescript#79, is in the typescript plugin, so they just have to fix it. There isn't much that we can do... Personally, I switched to https://www.npmjs.com/package/serverless-webpack long time ago. 🙂 |
I have circled back around to this and verified using serverless-webpack is the way to go. Solved my issues. |
I have run into this issue in a full typescript setup. serverless/serverless-plugin-typescript#79 was not enough to fix the issue for me, as I have (and need to keep)
It would be too costly for me to migrate to It works for me, but was wondering if there was a reason for not doing this? |
Every time I try and package I get:
I've spent a day and half combing through your issues and going through step by step guide with no joy. Any help is greatly appreciated:
The text was updated successfully, but these errors were encountered: