Skip to content
Use Vue.js with Playframework
Branch: master
Clone or download
Latest commit 389e26b Feb 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Update config.yml (#2) May 21, 2018
project Upgrade dependency versions (#30) Jan 17, 2019
src
test-play-project Small fix (#32) Feb 15, 2019
.gitignore
LICENSE
README.md Small fix (#32) Feb 15, 2019
build.sbt Update build.sbt Jan 17, 2019
package.json Support typescript (#24) Dec 15, 2018
version.sbt Update version.sbt Jan 17, 2019
yarn.lock

README.md

sbt-vuefy

CircleCI codecov Gitter chat

sbt-vuefy integrates Vue's single components into Playframework. It hot-reloads the changes of Vue components while running Playframework with sbt run. It also works with sbt stage, which triggers the production build.

Both Typescript and Javascript components are supported and can be mixed. Please see the example project in the folder test-play-project.

Also, see our blog post for some more detail: https://give.engineering/2018/06/05/vue-js-with-playframework.html

This plugin is currently used at GIVE.asia, which has more than 200 Vue components in both Javascript and Typescript.

Requirements

  • Webpack 4.x and vue-loader 15.x: you'll need to specify the webpack binary location and webpack's configuration localtion. This enables you to choose your own version of Webpack and your own Webpack's configuration. You can see an example in the folder test-play-project.
  • Playframework 2.6.x: This is because GIVE.asia uses Playframework 2.6. Anecdotally, I have been told that it doesn't work with Playframework 2.5
  • Scala 2.12.x and SBT 1.x: Because the artifact is only published this setting (See: https://bintray.com/givers/maven/sbt-vuefy). If you would like other combinations of Scala and SBT versions, please open an issue.

How to use

1. Install the plugin

Add the below line to project/plugins.sbt:

resolvers += Resolver.bintrayRepo("givers", "maven")

addSbtPlugin("givers.vuefy" % "sbt-vuefy" % "4.0.0")

The artifacts are published to Bintray here: https://bintray.com/givers/maven/sbt-vuefy

2. Configure Webpack config file.

Create webpack.config.js with vue-loader. Below is a working minimal example:

"use strict";

const VueLoaderPlugin = require('vue-loader/lib/plugin');

module.exports = {
  plugins: [new VueLoaderPlugin()],
  stats: 'minimal',
  module: {
    rules: [
      {
        test: /\.vue$/,
        loader: 'vue-loader',
      },
      {
        test: /\.scss$/,
        exclude: /node_modules/,
        use: [
          'vue-style-loader',
          'css-loader',
          'sass-loader'
        ],
      },
      {
        test: /\.ts$/,
        loader: 'ts-loader',
        options: {
          appendTsSuffixTo: [/\.vue$/],
        }
      }
    ]
  },
  resolve: {
    extensions: ['.ts', '.js', '.vue']
  }
};

You don't need to specify module.exports.output because sbt-vuefy will automatically set the field.

Your config file will be copied and added with some required additional code. Then, it will used by sbt-vuefy when compiling Vue components.

When running sbt-vuefy, we print the webpack command with the modified webpack.config.js, so you can inspect the config that we use.

To make it work with Typescript, tsconfig.json is also needed to be setup. Please see test-play-project for a working example.

3. Configure build.sbt

Specifying necessary configurations:

lazy val root = (project in file(".")).enablePlugins(PlayScala, SbtWeb, SbtVuefy) // Enable the plugin

// The commands that triggers production build when running Webpack, as in `webpack -p`.
Assets / VueKeys.vuefy / VueKeys.prodCommands := Set("stage")

// The location of the webpack binary. For windows, it might be `webpack.cmd`.
Assets / VueKeys.vuefy / VueKeys.webpackBinary := "./node_modules/.bin/webpack"

// The location of the webpack configuration.
Assets / VueKeys.vuefy / VueKeys.webpackConfig := "./webpack.config.js"

4. Find out where the output JS file is and how to use it

The plugin compiles *.vue within app/assets.

For the path app/assets/vue/components/some-component.vue, the output JS should be at http://.../assets/vue/components/some-component.js. It should also work with @routes.Assets.versioned("vue/components/some-component.js").

The exported module name is the camel case of the file name. In the above example, the module name is SomeComponent.

Therefore, we can use the component as shown below:

<script src='@routes.Assets.versioned("vue/components/some-component.js")'></script>

<div id="app"></div>
<script>
  var app = new Vue({
    el: '#app',
    render: function(html) {
      return html(SomeComponent.default, {
        props: {
          someData: "data"
        }
      });
    }
  })
</script>

Please see the folder test-play-project for a complete example.

Interested in using the plugin?

Please feel free to open an issue to ask questions. Let us know how you want to use the plugin. We want to help you use the plugin successfully.

Contributing

The project welcomes any contribution. Here are the steps for testing when developing locally:

  1. Run yarn install in order to install packages needed for the integration tests.
  2. Run sbt test to run all tests.
  3. To test the plugin on an actual Playframework project, go to test-play-project, run yarn install, and run sbt run.
  4. To publish, run sbt clean publish.

Future improvement

  • Currently, the plugin doesn't track CSS dependencies (e.g. using @import) because webpack/vue-loader doesn't track these dependencies. We need to find a way. See the ongoing issue: https://github.com/GIVESocialMovement/sbt-vuefy/issues/20
  • VueKeys.prodCommands is hacky. I use this approach because I don't have good understanding in SBT's scoping. There must be a better way of implementing the production build setting.
You can’t perform that action at this time.