Jay
Please feel free to open a PR!
Yeah if the PR describes what the fix is and has some tests that would be great.
@oakgary Thanks for putting together the repo. I'll have a look.
I figured out the problem with the repo. It has to do with the location of the tsconfig.json. It's placed outside the root of the service. If it is moved...
Getting back to this. @oakgary Did my PR not work for you? Because it worked for me. If it is because of the location of the `tsconfig.json`, we need to...
Yeah I'm digging into this issue now. It seems related to the babel loader that we are running `.ts` files through.
I've been spending some time on this one. I think I've got a sense for what is going on. Are you all using ``` "module": "commonjs" ``` in your `tsconfig.json`?...
@andrey-k Can you also set this in your `serverless.yml` and try again? ``` yml custom: bundle: caching: false ```
@andrey-k I might need a sample repo from you. I tried @oakgary's repo (https://github.com/oakgary/serverless-bundle-import-issue) with the following steps and it worked. ``` bash $ git clone https://github.com/oakgary/serverless-bundle-import-issue.git $ yarn #...
Yeah the issue is that with `commonjs` set, the exports conflict with the export set by the [babel-plugin-source-map-support](https://www.npmjs.com/package/babel-plugin-source-map-support) plugin. You shouldn't have to set it to `commonjs` in your `tsconfig.json`...