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

Allow custom module paths. #12

Closed
wants to merge 1 commit into from

Conversation

rwjblue
Copy link
Collaborator

@rwjblue rwjblue commented Apr 16, 2014

This allows for custom mapping of filenames to ES6 modules.

Specifically, in Ember we exclude lib from the generated module names, this provides a simple extension point to perform that kind of customization.

This allows for custom mapping of filenames to ES6 modules.

Specifically, in Ember we exclude `lib` from the generated module names,
this provides a simple extension point to perform that kind of
customization.
@joliss
Copy link
Owner

joliss commented Apr 17, 2014

For removing lib, if things need to be moved into place, I'd normally use broccoli-static-compiler on the tree to move things around, so that the file names come out correct.

In general, I try to keep my trees so that file paths correspond to module names, i.e. there is no top-level lib or similar.

So I'm not super-convinced by the use case, but I'd like to hear more.

@rwjblue
Copy link
Collaborator Author

rwjblue commented Apr 17, 2014

Interesting, I hadn't thought of doing it that way. I'll play around with transforming as a separate step and report back.

@rwjblue rwjblue closed this Oct 1, 2014
@rwjblue rwjblue deleted the allow-customized-module-paths branch October 1, 2014 02:36
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

Successfully merging this pull request may close these issues.

None yet

2 participants