givesocialmovement / sbt-webpack Goto Github PK

Hello,
I'd like to rebuild on changes in our *.vue files, but I can't seem to find the right setting.
I'm anything but a Scala dev, so these are just assumptions, but I'd guess this is handled by this includeFilter:
https://github.com/GIVESocialMovement/sbt-webpack/blob/master/src/main/scala/givers/webpack/SbtWebpack.scala#L36
But I don't really know how to change that from my build.sbt.
Is this even possible?

When webpack config's mode is set to production, the dependency-tree.json's content looks like below:

[{"output":"javascripts/node_modules.js","dependencies":[0]},{"output":"javascripts/vendor.js","dependencies":[2]},{"output":"javascripts/compiled.js","dependencies":[1,3,4]},{"output":"javascripts/compiled2.js","dependencies":[1,5]}]

This needs more investigation.

Hello Tanin,

Thanks for taking the time to develop this. I tried the very first steps to add the resolver and the plugin, however I face this issue:

Unresolved dependencies: givers.webpack#sbt-webpack;0.2.0: not found

Do you have any clue?

I work with @igreulich who helped with a few updates a year ago or so. Our project still depends on version 0.9.0. Since Bintray sunsetted their repository on May 1st (https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/), we can no longer pull this dependency from there.

Can you please update this project to publish to another repository. I specifically need version 0.9.0 to be published.

Thanks!

As the title says, a collegue couldn't run our project so we tried the included testproject which didn't create any js files.

We should support wildcard path in entry's input. At GIVE.asia, we have a use case where we want to compile all Javascripts in a folder into a single file.

The following in plugins.sbt doesn't resolve for me:

resolvers += Resolver.bintrayRepo("givers", "maven")
addSbtPlugin("givers.webpack" % "sbt-webpack" % "0.9.0")

Right now, sbt-webpack does not support external source-maps.

With webpack's devtool, broadly speaking, you have the option to create no source maps, inline source maps, or external source maps. As far as the plugin goes, webpack makes any source map you ask it to, but sbt-webpack does not move the external ones, or register them with sbt to be moved by the asset pipeline. As such, they are not available in the browser.

This is a problem when your app uses a tool like raygun.js to help with error monitoring. Raygun consumes the external source maps to point your errors to the right pieces of code in it's reports.

@tanin47 I have a new project for us, lol.

First, this is a discussion more than a bug, at least right now.

Per this line, if webpack did not change anything, it prints out some text in the console; 'No changes to compile.'

It doesn't SEEM to be accurate. I made a basic test project, mimicking our app's setup and config, but way smaller, you can see it here. Everytime I make a change to a.js or b.js webpack rebuilds, but then prints that string.

There also seems to be an issue where webpack does not rebuild if you modify files that are in it's bundle, but do not export something. (We use angular 1.7, and that is not an uncommon occurrence in ngjs.) I am looking into webpack specifically about that part. It might just be that without an export, webpack won't rebuild. (But I don't know yet.)

@tanin47

Playframework recompiles not only when the source file changes, but also when the output file change.

This happens because we build the relationship between the output file and all of its transitive dependencies.

Right now it seems infeasible to detect whether a source file is a immediate dependency of an output file when the output file is a product of file splitting.