Vue.js Single-File JavaScript Components in the Browser
Browser support for native JavaScript modules is finally happening. In this article, we show you what this means for Vue.js developers.
Join the DZone community and get the full member experience.
Join For FreeBrowser support for native JavaScript modules is finally happening. The latest versions of Safari and Chrome support them, Firefox and Edge will soon too.
One of the cool things about JavaScript modules for Vue.js users is that they allow you to organize your components into their own files without any kind of build step required.
In this article, I'm going to show you how to write a single-file component as a JavaScript module and use it in a Vue.js app. You can do this all in the browser without any Babel or Webpack!
When I say "single-file component" I'm talking about a single JavaScript file which exports a complete component definition. I'm not talking about the single .vue file you're used to. Sorry if you're disappointed. But I still think this is pretty cool, so check it out.
Project Setup
Let's use the vue-cli simple template to do this. That's right, the one without any Webpack.
xxxxxxxxxx
$ vue init simple sfc-simple
The complete code for this tutorial is in this GitHub repo if you want to download it.
Change into the directory and create the files we'll need:
xxxxxxxxxx
$ cd sfc-simple
$ touch app.js
$ touch SingleFileComponent.js
Remove the inline script from index.html and instead use script tags to link to our modules. Note the type="module" attribute:
xxxxxxxxxx
<html>
<head>
<title>Vue.js Single-File JavaScript Component Demo</title>
<script src="https://unpkg.com/vue"></script>
</head>
<body>
<div id="app"></div>
<script type="module" src="SingleFileComponent.js"></script>
<script type="module" src="app.js"></script>
</body>
</html>
Creating a Single-File JavaScript Component
This is a component like any other you've created, only you export the configuration object since it's a module:
SingleFileComponent.js
xxxxxxxxxx
export default {
template: `
<div>
<h1>Single-file JavaScript Component</h1>
<p>{{ message }}</p>
</div>
`,
data() {
return {
message: 'Oh hai from the component'
}
}
}
Now we can import it and use it in our Vue app:
app.js
xxxxxxxxxx
import SingleFileComponent from 'SingleFileComponent.js';
new Vue({
el: '#app',
components: {
SingleFileComponent
}
});
index.html
xxxxxxxxxx
<div id="app">
<single-file-component></single-file-component>
</div>
Serving the App
For a simple project like this all you need is a static server on the command line with the http-server module:
xxxxxxxxxx
# This will serve the project directory at localhost:8080
$ http-server
To view the app you will, of course, need to use a browser which supports JavaScript modules. I'm using Chrome 61.
Fallback
What if the user's browser doesn't support JavaScript modules? This will be the case for most users, for a while.
We can use a script tag with the nomodule attribute to write a simple error message to the document:
xxxxxxxxxx
<body>
<div id="app">
<single-file-component></single-file-component>
</div>
<script type="module" src="SingleFileComponent.js"></script>
<script type="module" src="app.js"></script>
<script nomodule>
document.getElementById("app").innerHTML = "Your browser doesn't support JavaScript modules :(";
</script>
</body>
A far better fallback, though, would be to use a Webpack bundled version of the project. This simple config will do the job:
xxxxxxxxxx
var path = require('path')
var webpack = require('webpack')
module.exports = {
entry: './app.js',
output: {
path: path.resolve(__dirname, './dist'),
publicPath: '/dist/',
filename: 'build.js'
},
module: {
rules: [
{
test: /\.js$/,
loader: 'babel-loader',
exclude: /node_modules/
}
]
}
}
After a build, the bundle can now be loaded as the fallback script:
xxxxxxxxxx
<body>
...
<script type="module" src="SingleFileComponent.js"></script>
<script type="module" src="app.js"></script>
<script nomodule src="/dist/build.js"></script>
</body>
This Webpack version will work identically in a browser without native module support. Here it is in Firefox, note that build.js has loaded and not the module:
Performance Comparison
Since we've now got two versions of the app available, one using the native JavaScript module system, and the other using Webpack, what performance difference is there?
Using the module system gives you a smaller project size. However, the Webpack project loads quicker overall.
Note: these figures are from a Lighthouse test with an HTTP/2 server.
I suspect preloading would improve the speed of the modules project, but we're a bit early for this to work:
Webpack is still the better choice for module-based architectures, but it's nice to know native modules are a thing.
Further Reading
Published at DZone with permission of Anthony Gore, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments