-
Braden Shepherdson authored
We do this for our JS and TS code. This change configures shadow-cljs to emit the source maps in release mode, and bumps the versions of shadow-cljs and the transitive dependency `source-maps-js` to enable webpack to consume these source maps correctly. (The output source maps have some quirks, and broke some consumers. Mainly that inlining of CLJS functions can result in empty namespaces, and while the file contents were correctly inlined, `sourceContents: ""` looks falsy in JS. Webpack would try to read the nonexistent source files and fail to build.)
Braden Shepherdson authoredWe do this for our JS and TS code. This change configures shadow-cljs to emit the source maps in release mode, and bumps the versions of shadow-cljs and the transitive dependency `source-maps-js` to enable webpack to consume these source maps correctly. (The output source maps have some quirks, and broke some consumers. Mainly that inlining of CLJS functions can result in empty namespaces, and while the file contents were correctly inlined, `sourceContents: ""` looks falsy in JS. Webpack would try to read the nonexistent source files and fail to build.)
Code owners
Assign users and groups as approvers for specific file changes. Learn more.