Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why am I submitting this PR
esbuild is a large dependency, and pinning to a specific version makes it less likely that it can be shared across other dependencies. To make i18next-parser lighter:
This is a potentially breaking change: if a someone uses a .ts i18next-parser configuration, doesn't have type stripping enabled (or has a configuration file that's incompatible with Node.js's type stripping), and doesn't otherwise have esbuild installed, then they'll have to install it.
Does it fix an existing ticket?
No
Checklist
yarn test(see details here) (Preexisting .ts functionality didn't have tests - if you want me to see about adding these, let me know.)