feat: Replace entries
option with releaseInjectionTargets
#123
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.
We faced problems when dogfooding the bundler plugin in https://github.com/getsentry/gib-potato.
We tried to inject the release in non-JS files.
.js
,.ts
,.jsx
,.tsx
,.cjs
or.mjs
).Considering the above fixed, if an app's entry point was a non-JS file (e.g. a
.html
file) we didn't inject the release anywhere at all.entries
option with a newreleaseInjectionTargets
option to allow for more fine-grained control in overriding in which modules the release code should be injected. This is a breaking change so we added an entry in the migration docs.