Skip to content

Commit 1687df1

Browse files
ADI1133benvinegar
authored andcommitted
[Docs] Fix map.js vs js.map confusion
1 parent 3679c1d commit 1687df1

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/sourcemaps.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ that maps the minified code back to the original source:
2727

2828
node_modules/uglify-js/bin/uglifyjs {input} \
2929
--source-map-root={relroot}/ \
30-
--source-map-url={name}.map.js \
31-
--source-map={relpath}/{name}.map.js \
30+
--source-map-url={name}.js.map \
31+
--source-map={relpath}/{name}.js.map \
3232
--source-map-include-sources \
3333
-o {output}
3434

@@ -52,7 +52,7 @@ Webpack can be configured to output source maps by editing webpack.config.js.
5252
output: {
5353
path: path.join(__dirname, 'dist'),
5454
filename: "[name].js",
55-
sourceMapFilename: "[name].map.js",
55+
sourceMapFilename: "[name].js.map",
5656
}
5757
};
5858

@@ -106,15 +106,15 @@ on the last line, the following directive is found:
106106

107107
.. code-block:: javascript
108108
109-
//# sourceMappingURL=app.map.js
109+
//# sourceMappingURL=app.js.map
110110
111-
Sentry will attempt to fetch ``app.map.js`` from http://example.org/js/app.map.js.
111+
Sentry will attempt to fetch ``app.js.map`` from http://example.org/js/app.js.map.
112112

113113
Alternatively, during source map generation you can specify a fully qualified URL where your source maps are located:
114114

115115
.. code-block:: javascript
116116
117-
//# sourceMappingURL=http://example.org/js/app.map.js
117+
//# sourceMappingURL=http://example.org/js/app.js.map
118118
119119
While making source maps available to Sentry from your servers is the easiest integration, it is not always advisable:
120120

@@ -172,7 +172,7 @@ if a browser (or filesystem) had to resolve its path. So for example, if your so
172172
reference is just a relative path, it's **relative to the location of the referencing file**.
173173

174174
So for example, if you have ``http://example.com/app.min.js``, and the file contains the
175-
reference to ``app.map.js``, the name of the uploaded file should be ``http://example.com/app.map.js``.
175+
reference to ``app.js.map``, the name of the uploaded file should be ``http://example.com/app.js.map``.
176176

177177
.. code-block:: bash
178178

0 commit comments

Comments
 (0)