Skip to content
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

Consider releasing as multiple separate modules #47

Open
tomek-he-him opened this issue Jul 20, 2015 · 2 comments
Open

Consider releasing as multiple separate modules #47

tomek-he-him opened this issue Jul 20, 2015 · 2 comments

Comments

@tomek-he-him
Copy link

I used to think of the trine/boolean/and way of distributing modules as bullseye. Super simple, built into the language.

But I’ve recently had a very interesting conversation which led me to change my mind: mattdesl/module-best-practices#2. The gist of it is “this breaks things”. It might convince you as well.

@jussi-kalliokoski
Copy link
Owner

Yes, this is actually something I've been intending to do - Trine was built with this in mind, however, for quick access one main module is also handy, like with lodash - this allows for optimizing for footprint later on in the development process instead of paying the discovery price upfront (also allows for building better editor autocompletion). The build process already has a separate main folder that gets published, all that's left to do is to add the source transforms and dependency mappings for the separate modules to make this work. I haven't had the time to do this myself yet, and would also be more than happy to take PRs for this. :)

@gajus
Copy link

gajus commented Nov 14, 2016

Is there still active development going on here or has this package been superseded by something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants