You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2024. It is now read-only.
There is --keep-names option in esbuild that keeps function names from being changed, which is exactly what I need. Can the zip-it-and-ship-it esbuild bundler expose that option?
The text was updated successfully, but these errors were encountered:
Yes, this would also enable working around this issue with older versions of node-fetch which e.g. googleapis still rely on: node-fetch/node-fetch#784 (comment)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
- Do you want to request a feature or report a bug?
Feature request
- What is the current behavior?
My app uses a module that checks the functions'
name
property during validation (https://github.com/graphql-compose/graphql-compose-mongoose/blob/e4b916bf4c7a2e8857345ac9476d4e76bc25e030/src/resolvers/findById.ts#L42-L44). By default, esbuild renames functions during bundling, which changes theirname
property, which causes that check to fail.- What is the expected behavior?
There is
--keep-names
option in esbuild that keeps function names from being changed, which is exactly what I need. Can the zip-it-and-ship-it esbuild bundler expose that option?The text was updated successfully, but these errors were encountered: