-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generic loading of moazik-ext-* stuff #60
Comments
One way I guess would be to rewrite everything with webpack/css-modules, and have the components come with their styles and everything.. |
Yep,I totally agree with the webpack switch, it could be better, but moving to webpack requires a lot of work, there's already an issue on this, it seems someone has started something :). |
A fix should be to try to find the node modules directory and use its path instead of the hardcoded one. |
One suggestion was to look for |
|
What is the best way to start developing extensions? For example if I move my extension into the node_modules folder of my dashboard, it somehow doesn't listen to mixins. |
@kurtextrem, this problem often occurs when you have several modules duplicated, locally, I use |
@plouc I have a funny other issue now: |
@kurtextrem, sorry for the late reply, can you share your |
@benediktvaldez, Mozaïk v2 now uses webpack, see installation instructions here. |
I close this issue as there's not much activity and the original issue should be solved with webpack. |
My situation is that node_modules is not located in the same folder as my code, but your built-in
gulp build
assumes otherwise (understandably I suppose)Ideally we could find a way to load all modules that start with
mozaik-ext-
regardless of wherenode_modules
is locatedOne example
Not sure how we could solve this - just throwing this out there for now 😸
The text was updated successfully, but these errors were encountered: