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
There was also a problem with TypeScript completion items containing a large number of tokens (a token is the internal name of the item being exported).
Background
In
css-loader@7
,namedExport
now defaults totrue
(I'm not sure of the motivation behind this change.).18.12.0
webpack-contrib/css-loader#1583So
css-loader@7
forces you to import CSS Modules files as follows:On the other hand,
happy-css-modules
generates.d.ts
with default export.happy-css-modules/packages/example/01-basic/1.css.d.ts
Lines 1 to 21 in 6133916
Therefore
happy-css-modules
forces you to import CSS Modules files as follows:This causes compatibility problems.
My opinion
I don't know how to solve this.
happy-css-modules
previously supported--namedExport
option. However, it was removed due to problems with definition jumps not working.There was also a problem with TypeScript completion items containing a large number of tokens (a token is the internal name of the item being exported).
For this reason, I think we should not support
--namedExport
option.Workaround
Please set the
namedExport
option tofalse
in css-loader.The text was updated successfully, but these errors were encountered: