Zack Sheppard

Actually, digging into it, I think this is a duplicate of (or at least closely related to) #205 - my `stage` uses the format of `stage: ${opt:stage, self:custom.defaultStage}` to allow...

Might it be possible to solve this using a `hook` command like the [website component](https://github.com/serverless-components/website) does? Then it would be possible to configure the component to use webpack to transpile...

> EDIT: Hey just for future folks who come across this thread - even though I came up with a possible workaround for this problem last year and have merged...

> EDIT: Hey just for future folks who come across this thread - even though I came up with a possible workaround for this problem last year and have merged...

I'm glad it was helpful @freddieerg. Since this was 3 months ago, I don't remember with 100% accuracy but as I recall the app.js name is hard-coded in the code...

Great news, thanks for the update @freddieerg

I would love to see a PR adding functionality like this merged in, though I agree with @jacksontaylor13 that it would be best to do so as a per-animation configuration...

Since there's been no move on this for a while, I created a fork that solves this problem: https://github.com/travelerdev/nestjs-sentry This separates out two packages `@travelerdev/nestjs-sentry` and `@travelerdev/nestjs-sentry-graphql` which are identical...

Last commit was back in January - @ntegral are you around or should we migrate to a fork?

In the meantime, I've created a fork as well - https://github.com/travelerdev/nestjs-sentry It upgrades to NestJS 9.x support, as well as Sentry 7.x and separates out dependencies on `@nestjs/graphql` into their...