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
Also, please pay attention to the source map of js file which is also generated in this example, contains correct path for sources:
"build/test.js.map"
Okay, it seems I've just found a workaround for this - it's necessary to pass "to" attribute via options, e.g.:
//
rollupPluginPostCss({ sourceMap: true, modules: true, extract: "styles.css", to: path.resolve("./build/styles.css") })
//
As a result the source location looks like this:
Given that, the source files hierarchy looks like this:
content of test.js file:
And the Rollup config looks like this:
And devDependencies look like this:
When I run rollup build
rollup -c rollup.config.mjs
the source map of css looks like this:"build/styles.css.map"
Please pay attention that folders hierarchy is missed here. Expected behavior:
Also, please pay attention to the source map of js file which is also generated in this example, contains correct path for sources:
"build/test.js.map"
The text was updated successfully, but these errors were encountered: