Prefer selecting 'bundle' artifacts over 'non-bundle' artifacts #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the scalajs-bundler sbt plugin and deploying to Heroku, I've had problems with the
project-opt.js
artifact being selected over theproject-opt-bundle.js
artifact which is required - I think-bundle
artifacts should be preferred -selectScript.scala.html
only selects one, so it should be the-bundle
one.This follows on from #17.
Until this fix is released, a workaround for this issue is to hack the value of the
resourceExists
function sent toselectScript.scala.html
, eg adding&& name.contains("-bundle")
: