Conversation
size-limit report 📦
|
Lms24
left a comment
There was a problem hiding this comment.
This looks overall very good to me. I think it covers everything related to the linked tasks. I just had some minor suggestions/comments which by all means are mostly optional.
| **CDN bundles of version 7 or higher will no longer be distributed through our npm package.** | ||
| This means that most third-party CDNs like [unpkg](https://unpkg.com/) or [jsDelivr](https://www.jsdelivr.com/) will also not provide them. | ||
|
|
||
| If you depend on any specific files in a Sentry JavaScript npm package, you will most likely need to update their references. |
There was a problem hiding this comment.
Should we give an example of changing an import from e.g. @sentry/somePkg/dist/... to @sentry/somePkg (recommended) or @sentry/somePkg/cjs/.. (if really necessary)?
MIGRATION.md
Outdated
|
|
||
| If you depend on any specific files in a Sentry JavaScript npm package, you will most likely need to update their references. | ||
|
|
||
| ### Removing the `API` class from `@sentry/core`` |
There was a problem hiding this comment.
| ### Removing the `API` class from `@sentry/core`` | |
| ### Removing the `API` class from `@sentry/core` |
MIGRATION.md
Outdated
|
|
||
| ### Restructuring Of Package Content | ||
|
|
||
| Up until now, we have published our packages on npm with the following structure: |
There was a problem hiding this comment.
Sorry for the nit but I think it's better to be specific here. Totally optional though.
| Up until now, we have published our packages on npm with the following structure: | |
| Up until v6.x, we have published our packages on npm with the following structure: |
MIGRATION.md
Outdated
|
|
||
| ### Removing the `API` class from `@sentry/core`` | ||
|
|
||
| The internal `API` class was removed. More details can be found in the [PR that deprecated this class](https://github.com/getsentry/sentry-javascript/pull/4281). To migrate, see the following example. |
There was a problem hiding this comment.
Again an optional suggestion but for me it makes sense to specify that the functionality is not lost (if I understand the PRs correctly).
| The internal `API` class was removed. More details can be found in the [PR that deprecated this class](https://github.com/getsentry/sentry-javascript/pull/4281). To migrate, see the following example. | |
| The internal `API` class was removed in favour of functions. More details can be found in the [PR that deprecated this class](https://github.com/getsentry/sentry-javascript/pull/4281). To migrate, see the following example. |
|
I'm gonna go ahead and merge this in so we can iterate on it as needed. |
|
we kinda messed up the commit name here but whatever |
Documents: - ES6 for CJS files - Dropping Support for Node v6 - Removing Platform Integrations - New npm package structure - Deleting deprecations
Documents: - ES6 for CJS files - Dropping Support for Node v6 - Removing Platform Integrations - New npm package structure - Deleting deprecations
Documents: - ES6 for CJS files - Dropping Support for Node v6 - Removing Platform Integrations - New npm package structure - Deleting deprecations
Documents: - ES6 for CJS files - Dropping Support for Node v6 - Removing Platform Integrations - New npm package structure - Deleting deprecations
Documents: - ES6 for CJS files - Dropping Support for Node v6 - Removing Platform Integrations - New npm package structure - Deleting deprecations
This is adding a migration guide for migrating from 6.x to 7.x.
Currently the following changes need to be documented:
Please let me know if I forgot something in the list above!
Ref: