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

Do not assume browserify #29

Closed
juandopazo opened this issue Jan 7, 2014 · 7 comments
Closed

Do not assume browserify #29

juandopazo opened this issue Jan 7, 2014 · 7 comments

Comments

@juandopazo
Copy link

Would it be possible not to assume the use of browserify? It would just mean:

  • Not assuming global is available
  • Using a UMD pattern

Thanks!

@kriskowal
Copy link
Owner

Oh, yes, the recent inclusion of @petkaantonov’s Queue did carry the assumption of a CommonJS module system, and I forgot that we had not met the AMD and <script> users’ needs. My intent is that we provide a build system that produces AMD and <script> versions, as we do in Q master.

@juandopazo
Copy link
Author

If you think that's necessary, how about using ES6 modules and transpile using https://github.com/square/es6-module-transpiler/?

@kriskowal
Copy link
Owner

In due time. For now, CommonJS is my preference.

@juandopazo
Copy link
Author

FWIW I'm considering importing asap into YUI and ES6 modules would help me transpile to YUI modules.

@kriskowal
Copy link
Owner

See #42, #43, #44.

@juandopazo
Copy link
Author

👍

@marekjalovec
Copy link

at least fix global variable please, it's breaking build for webpack users mozilla/nunjucks#520

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

No branches or pull requests

3 participants