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

Processing entry-point dependencies. #5

Merged
merged 5 commits into from
Apr 28, 2016

Conversation

furious-luke
Copy link
Contributor

Hello! I noticed that the compiler would not run when a dependent JS file which is required in the entry-point file was modified, meaning the browserified output would be incorrect until the entry-point file itself was modified.

I've just modified the is_outdated method to generate a list of dependencies and check if any of them are out of date as compared to the compiled browserified file.

One thing to note is that it may very well be the case that the command to generate the list of dependencies takes just as long as actually compiling, which would mean we could simply force a recompile every time and it would take the same amount of time. Given that, it may not actually be worth while merging this pull request in, I just though I'd open it and give you the opportunity to do so if you wished.

Thanks!

Luke Hodkinson and others added 4 commits October 14, 2015 18:50
all dependencies. I was finding that if I `required`d files that
also lived in my static files folders from my entry-point files,
then any changes to the dependent files would not result in recompiling
the entry-point file.
@j0hnsmith
Copy link
Owner

Can you rebase to resolve the conflicts, then I'm happy to merge. Thanks

@furious-luke
Copy link
Contributor Author

Okay, conflicts have been resolved.

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.

2 participants