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

Parameterize output module format #16

Closed
mstade opened this issue Feb 26, 2016 · 2 comments
Closed

Parameterize output module format #16

mstade opened this issue Feb 26, 2016 · 2 comments

Comments

@mstade
Copy link
Member

mstade commented Feb 26, 2016

We currently assume AMD as the output module format, something which may or may not change down the line, but is crucial to make things run in a production environment. That said, in development, it may be useful to output different formats. For instance, running tests in a non-browser environment may well be easier with CJS rather than AMD. Additionally, in a development environment, globals may even offer development server capabilities such as reloading modules on the fly, much like figwheel does for ClojureScript.

So the proposal is as such:

  • Add a --modules option with the following possible values: amd, cjs, umd, global, system
  • Ignore the --modules option when combined with --production, in which case amd will be used
@mstade
Copy link
Member Author

mstade commented Feb 26, 2016

Come to think of it, maybe --modules should not be ignored in conjunction with --production, just that it should always default to amd... This would have the interesting effect that ez-build could build itself.

@mstade
Copy link
Member Author

mstade commented Aug 8, 2016

Closing because #23.

@mstade mstade closed this as completed Aug 8, 2016
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

1 participant