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
Updating the tarball structure will be a breaking change for anyone who explicitly imports modules from the replay package. This is fine, as we're not yet stable and we're jumping major versions from 0.x to 7.x anyway. Also, this is an edge case scenario and definitely not something that concerns the majority of our users. More info: getsentry/sentry-replay#321
Build changes have the potential to cause bugs and issues. We'll have to be careful. Verifying the tarball contents before it is released is absolutely necessary.
Closing this as I think the high-prio items are complete for the time being. We still have a few open ToDos around Eslint and smaller build changes (version replacement mainly) but we can do this iteratively later on.
After merging in replay, with only minimal changes, we need to apply our monorepo's build config to the replay package.
To Do:
.eslintrc.js
config #6302tsconfig.json
s #6308build
directory structure with other packages (esm, cjs, types)build:types
, adjustbuild:rollup
)package.json
scripts #6348Risks:
Updating the tarball structure will be a breaking change for anyone who explicitly imports modules from the replay package. This is fine, as we're not yet stable and we're jumping major versions from 0.x to 7.x anyway. Also, this is an edge case scenario and definitely not something that concerns the majority of our users. More info: getsentry/sentry-replay#321
Build changes have the potential to cause bugs and issues. We'll have to be careful. Verifying the tarball contents before it is released is absolutely necessary.
ref: #5326
The text was updated successfully, but these errors were encountered: