Fixed path config changes not published on npm

Question

Fixed path config changes not published on npm

xameeramir opened this issue 5 years ago · comments

the tsconfig path logic in your npm is breaking because the latest commits are pushed to the npm

Andrew Turner · Answer 1 · Mon Oct 12 2020 07:40:13 GMT+0800 (China Standard Time)

I'm encountering what I think this issue is referring to.

This line changes the handler to the outDir which is typically dist. however tsconfig.json compiles to {outDir}/src (or whatever your code paths are). So when deploying, at least in AWS, the code is trying to run dist/handler.js instead of src/handler.js.

Can this be patched + redeployed?