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
~fastOptJS runs non-stop #1491
Comments
Would the output of fastOptJS perchance appear in the watched sources of the enclosing project? |
No, but do you know of a means by which I can verify that? What may be relevant is that there is a symlink in I wouldn't think the symlink would be the cause because 1) it worked in 0.5.x, and 2) the symlink itself doesn't change when is running |
Hum, OK, I'll investigate this. |
Well, I think we broke this in 07b8871. By turning the classes representing the JS_DEPENDENCIES from case classes to normal classes, we broke their |
Fix #1491: Give proper equals/hashCode to JSDependencyManifest.
👍 |
…cyManifest. This is necessary for the sbt plugin to avoid recreating the JS_DEPENDENCIES file over and over again, constantly invalidating the output of fastOptJS and fullOptJS.
In my SBT build, I have a Scala.JS-based
webapp-client
module, which is part of an aggregate module calledwebapp
, which itself is part of the root aggregate module.;project webapp-client; ~fastOptJS
works as expected by only building once, then waiting for changes.However from one of the aggregate modules,
~webapp-client/fastOptJS
keeps regenerating the JS again and again. This wasn't the case before 0.6.0.The text was updated successfully, but these errors were encountered: