Dwight Watson's blog

Configuring Webpack externals with Webpacker

This blog post was originally published a little while ago. Please consider that it may no longer be relevant or even accurate.

Webpack provides a feature known as externals which allows you to instruct it not to bundle any assets that you will provide externally at runtime. It's useful if you're going to serve assets from another location or don't want an asset to be bundled up.

It's easy enough to hook up as well, but here's how you would go about doing it with Rails Webpacker in the environment.js file. You simply piggy-back off the default configuration provided by Webpacker and export it out as per usual.

const { environment } = require('@rails/webpacker')

environment.config.externals = {
jquery = 'jQuery'

module.exports = environment

The key in the extenals object is the name of the module you'd be importing in your app and the value will be the name of that module as it's provided at runtime. In the above example it could instead be $ if you so desired.

A blog about Laravel & Rails by Dwight Watson;

Picture of Dwight Watson

Follow me on Twitter, or GitHub.