Closed agubler closed 7 years ago
@agubler Investigated
I have version 2.0.0-beta1.4
installed (latest on npm)
npm webpack.config.js
has (gif|png|jpe?g|svg)
but here in the master it is (gif|png|jpe?g|svg|eot|ttf|woff|woff2)
So maybe it is already resolved but not on npm. Could I simply swap the webpack.config.js
?
@sebilasse you should be able to just install 2.0.0-beta2.1
OK. Did not know. https://github.com/dojo/meta an npm said 1.4 is latest. Thanks.
Yes latest
is the same as beta1
if you need to get a more recent "development" release then you can use the next
tag or a specific version.
Please can you close out the issue if using the latest release resolves the issue, thanks!
@agubler It does not ...
"spec": "2.0.0-beta2.1",
after some more hours of investigating (same issue for many users of css-modules) :
The workaround ~ as module root
did not work.
My workaround is to use absolute paths. But this is not suitable because a lot of CSS frameworks
(e.g. Bootstrap / Semantic) use relative paths ...
@sebilasse can you run dojo version --o
just to confirm that you get:
build (@dojo/cli-build-webpack) 2.0.0-beta2.1 (on latest stable version).
we are using relative paths and assorted font file formats in our internal projects fine after https://github.com/dojo/cli-build/pull/148
@matt-gadd build (@dojo/cli-build-webpack) 2.0.0-beta1.4 (can be updated to 2.0.0-beta2.1).
This would mean I have to update the node modules in all 138 semantic ui widgets. Can I somehow use the globally installed cli-build ?
@agubler I would later do an issue about updating in dojo/meta.
I have rearranged the project structure to one huge dojo app wherein I develop all semantic ui widgets.
So now I only need to update one folder but somehow then dojo build webpack --element
is not working (can I create all webcomponents in the app in combination with build
?) –
The issue here is maybe the sentence in the Readme
to use @dojo/cli-build in every project, install the project globally
This won't work because a local @dojo/cli-build
is installed alongside with each project ...
However, apart from this, the issue can be closed. But I am not able to close it (after moving to this repo) ...
Closing this issue as it seems to be related to an outdated version of cli-build-webpack
.
@sebilasse commented on Fri Jun 02 2017
The same happens for every font file (eot, otf) and many other files that can be imported in CSS. Apart from that
reserved TypeScript word
s do not work but many well known CSS libraries have classes like e.g..delete.icon
...Maybe this issue helps https://github.com/css-modules/css-modules/issues/95
@agubler commented on Fri Jun 02 2017
@sebilasse this would be a
@dojo/cli-build
issue