optimal js module design
@Zach Jensz shared me this article after looking at the source code for xoram.dev.
While I understand the premise of the article and agree with them, I think I'm mostly good on for the
On top of that, you would use close to all the exported code in an actual use case, any non-default feature being it's own package under
(for example the yet to be documented
My question is then the following :
Assuming the article's author is right in their observations, am I right to believe I'm in a situation where they don't apply ?
While I understand the premise of the article and agree with them, I think I'm mostly good on for the
@xoram/coreOn top of that, you would use close to all the exported code in an actual use case, any non-default feature being it's own package under
@xoram/plugin-[packagename](for example the yet to be documented
@xoram/plugin-panoramiqueMy question is then the following :
Assuming the article's author is right in their observations, am I right to believe I'm in a situation where they don't apply ?
Perhaps the most acute yet least recognized problem in the JavaScript ecosystem is the widespread lack of understanding of optimal module design.
GitHub
A lightweight plugin framework for modular applications. - Ragnar-Oock/xoram
npm
xoram core. Latest version: 0.1.0, last published: 4 days ago. Start using @xoram/core in your project by running
npm i @xoram/corenpm
A dynamic VueJS integration for xoram. Latest version: 0.1.0, last published: 4 days ago. Start using @xoram/plugin-panoramique in your project by running
npm i @xoram/plugin-panoramique
A friendly place for developers to meet other devs, ask questions, get help, and just have a good time 🙂.
36,263Members
Resources
Was this page helpful?
