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

mimosa watch + module config, cannot update on the fly #24

Closed
dbashford opened this issue Oct 20, 2013 · 2 comments
Closed

mimosa watch + module config, cannot update on the fly #24

dbashford opened this issue Oct 20, 2013 · 2 comments

Comments

@dbashford
Copy link
Owner

You cannot run mimosa watch and have mimosa run and re-run modules based r.js runs.

One reason is because of source maps. The initial build has no issues, source maps work, but the next build after starting mimosa watch will have issues because of all the source map artifacts in place after the first build. So, need to, by default, disable source maps for modules runs, but allow via require.optimize.overrides to force source maps for those that need it for a single run.

Another reason is because the original module files get written over during the build with the optimized files. So need to cache the originals and slide them in before restarting a build

@dbashford
Copy link
Owner Author

From dbashford/mimosa#297

@dbashford
Copy link
Owner Author

This commit did most of the work: c37e2e0

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

1 participant