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
feat(docs): Add enum removal and deprecation section to migration docs (#4938)
list the removed enums in v7 and the ones we chose to keep deprecated until the next major release. Additionally, provide links to examples how to migrate to string literals for the public enums.
Co-authored-by: Luca Forstner <[email protected]>
Copy file name to clipboardExpand all lines: MIGRATION.md
+27-8
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
-
##Upgrading from 6.x to 7.x
1
+
# Upgrading from 6.x to 7.x
2
2
3
3
The main goal of version 7 is to reduce bundle size. This version is breaking because we removed deprecated APIs, upgraded our build tooling, and restructured npm package contents.
4
4
Below we will outline all the breaking changes you should consider when upgrading.
5
5
6
-
###Dropping Support for Node.js v6
6
+
## Dropping Support for Node.js v6
7
7
8
8
Node.js version 6 has reached end of life in April 2019. For Sentry JavaScript SDK version 7, we will no longer be supporting version 6 of Node.js.
9
9
10
10
As far as SDK development goes, dropping support means no longer running integration tests for Node.js version 6, and also no longer handling edge cases specific to version 6.
11
11
Running the new SDK version on Node.js v6 is therefore highly discouraged.
12
12
13
-
###Removal Of Old Platform Integrations From `@sentry/integrations` Package
13
+
## Removal Of Old Platform Integrations From `@sentry/integrations` Package
14
14
15
15
The following classes will be removed from the `@sentry/integrations` package and can no longer be used:
16
16
@@ -21,19 +21,19 @@ The following classes will be removed from the `@sentry/integrations` package an
21
21
These classes have been superseded and were moved into their own packages, `@sentry/angular`, `@sentry/ember`, and `@sentry/vue` in a previous version.
22
22
Refer to those packages if you want to integrate Sentry into your Angular, Ember, or Vue application.
23
23
24
-
###Moving To ES6 For CommonJS Files
24
+
## Moving To ES6 For CommonJS Files
25
25
26
26
From version 7 onwards, the CommonJS files in Sentry JavaScript SDK packages will use ES6.
27
27
28
28
If you need to support Internet Explorer 11 or old Node.js versions, we recommend using a preprocessing tool like [Babel](https://babeljs.io/) to convert Sentry packages to ES5.
29
29
30
-
###Renaming Of CDN Bundles
30
+
## Renaming Of CDN Bundles
31
31
32
32
CDN bundles will be ES6 by default. Files that followed the naming scheme `bundle.es6.min.js` were renamed to `bundle.min.js` and any bundles using ES5 (files without `.es6`) turned into `bundle.es5.min.js`.
33
33
34
34
See our [docs on CDN bundles](https://docs.sentry.io/platforms/javascript/install/cdn/) for more information.
35
35
36
-
###Restructuring Of Package Content
36
+
## Restructuring Of Package Content
37
37
38
38
Up until v6.x, we have published our packages on npm with the following structure:
39
39
@@ -54,7 +54,7 @@ If you depend on any specific files in a Sentry JavaScript npm package, you will
54
54
For example, imports on `@sentry/browser/dist/client` will become `@sentry/browser/cjs/client`.
55
55
However, directly importing from specific files is discouraged.
56
56
57
-
###Removing the `API` class from `@sentry/core`
57
+
## Removing the `API` class from `@sentry/core`
58
58
59
59
The internal `API` class was removed in favor of the `initAPIDetails` function and the `APIDetails` type. 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.
0 commit comments