João Dias
João Dias
I was updating to v5 because I'm using Apollo Server and wanted to get rid of the fork. I wasn't considering v6 because it installs too many packages that we...
Is there any hope to get this in?
Perhaps we can re-target for v2 instead of main branch?
Alright, fair enough
Our use case is to use AWS API to call lambdas directly instead of having an API Gateway in front of them
We are in the same boat as @decline. Also want to move away from `yarn v1` but it's really difficult having to keep running `ngcc` to only compile @sentry/angular ):
I also just got hit by this bug but it's not related to spack. The `transformer` API from core also triggers the same bug
Sorry, I ended up using rspack for what I wanted to do and no longer have that problematic piece of code ):
Can this be prioritised? `escodegen` depends on an outdated version of `optionator` which depends on `word-wrap` which has a security alarm in our pipelines
I guess there's no hope for this. Is there any other modern package that can do the same thing?