Closed grossmannmartin closed 4 months ago
I don't understand why this is happening to you and why would adding things to exports
solves this.
The CSS does exists in the ./dist
folder since the exports
does not have rewrite rule for CSS
files your import should work, as it does for me when I test Tagify and can be seen to work in the live Codesandbox React demo.
exports
is only for aliasing so I cannot see why would you use it to point the same path to itself..
when this issue started for you?
The latest update to the version 4.25.0 introduces this issue. it is working till 4.24.0
@yairEO TBH, I'm not so profound with the webpack to know how it's possible.
You can check our package.json and webpack.config.js if you're interested.
The version 4.24.0 works fine as @AnujShr mentioned earlier.
If I install 4.25.0, the error starts popping during the npm run build
process.
And if I manually edit the node_modules/@yaireo/tagify/package.json
file and add the line from this PR, the build finishes successfully 🤷♂️
edit: According to this https://webpack.js.org/guides/package-exports/
When the exports field is specified, only these module requests are available. Any other requests will lead to a ModuleNotFound Error.
Having same issue here, using vite
same here, using vite
will merge and release a new version
Just pushed the new version:
Hi, our build just starts failing on
The CSS file is imported in our *.less file and processed by Webpack
Adding the proposed export fixes the problem on our end. If it's intentional and the CSS file should be used differently, I would appreciate the info :)
Thanks