-
Notifications
You must be signed in to change notification settings - Fork 2
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
Infrastructure compile type checking errors #11
Comments
|
That's odd - you shouldn't need to install Could you check that you've still got that file in your copy? I've checked and it's definitely in |
Yeah I have that file. I seem to be getting all kinds of different errors trying to use my local npm linked version of the plugin. Currently:
I don't know where |
Hey @revmischa, just published 0.7.0. I'd be interested to know if that fixes these issues? |
Installed it, here's where I'm at right now:
Wondering if this error is related to serverless/serverless-plugin-typescript#170 |
I'm trying the more maintained fork https://www.npmjs.com/package/@kingdarboja/serverless-plugin-typescript but still seeing the same error. Maybe we have competing tsconfig files? Or plugin-ts is deleting the .build dir before aws-cdk tries to use it or something?
|
Interesting - when it fails, does |
Yes, |
I've managed to repro locally too - it looks like |
@revmischa I've pushed a change in #13 - would you be able to give it a go? It seems like our logic to pick up the deployment package wasn't correct for packages generated by |
|
It says |
I do however have
|
If I set
Maybe because I'm running a local version and not the npm module? |
Yeah, that seems like it could be the issue. For testing locally, I've been doing the following from my service directory: SERVERLESS_AWS_CDK_PATH=../serverless-aws-cdk
pushd ${SERVERLESS_AWS_CDK_PATH} && \
npm i && npm run build && npm pack && popd && \
rm -rf node_modules && npm i && npm install ${SERVERLESS_AWS_CDK_PATH}/serverless-aws-cdk-0.7.0.tgz
SLS_DEBUG=* npm run sls -- deploy -s dev Not sure if that'll help in your case? If not, happy to publish another version with the function path fix tomorrow morning and see if that sorts it! |
Yep that works! Thanks! |
It does try to deploy to CF but errors:
Same result after doing |
From that output (and from the |
Oh yeah, I used the config from the example |
The text was updated successfully, but these errors were encountered: