Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/infinum/webpack-asset-pipeline
🚀 A missing link for the asset pipeline alternative with Webpack.
https://github.com/infinum/webpack-asset-pipeline
asset-pipeline assets manifest plugin rails webpack
Last synced: about 2 months ago
JSON representation
🚀 A missing link for the asset pipeline alternative with Webpack.
- Host: GitHub
- URL: https://github.com/infinum/webpack-asset-pipeline
- Owner: infinum
- License: mit
- Archived: true
- Created: 2016-09-26T18:20:20.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2019-07-21T04:43:38.000Z (over 5 years ago)
- Last Synced: 2024-09-18T01:39:07.984Z (about 2 months ago)
- Topics: asset-pipeline, assets, manifest, plugin, rails, webpack
- Language: JavaScript
- Homepage: https://infinum.co/the-capsized-eight/squeezing-webpack-into-backend-frameworks
- Size: 115 KB
- Stars: 30
- Watchers: 9
- Forks: 5
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
webpack-asset-pipeline
==============================
[](https://greenkeeper.io/)
A missing link for the asset pipeline alternative with Webpack.
[](https://semaphoreci.com/infinum/webpack-asset-pipeline) [](https://badge.fury.io/js/webpack-asset-pipeline)
This plugin can be used to flush a list of your assets to a `manifest.json` file and replace the asset pipeline.
## Usage
This is a Webpack plugin that creates a manifest file for your assets. It can output files to Webpack (as emitting) or as a file on the filesystem.
```
npm install --save-dev webpack-asset-pipeline
```
In your `webpack.config.js` file specify the plugin:
```JavaScript
const WebpackAssetPipeline = require('webpack-asset-pipeline');
{
plugins: [
new WebpackAssetPipeline()
]
}
```
You'll find the `manifest.json` file in your output directory. You can read more about the options [here](documentation/options.md).
## Requiring images
All images have to be required in the JavaScript in order for webpack to process them, except the ones you require in your scss file (because wepback is processing your scss file adready)
You can create a new file which will hold all the images, e.g. `files.js`
```JavaScript
require('images/file1.jpg');
require('images/file2.jpg');
require('images/file3.jpg');
```
And then in `application.js` (your entrypoint)
```JavaScript
require('files');
```
You can see an example configuration and its documentation [here](example/README.md).
## Output
Once you set everything up, you should see this in your `manifest.json` file:
```JavaScript
{
"images/file1.jpg": "963eb32907744d9a0d6b98127162808f.jpg",
"images/file2.jpg": "162808f4d9a0963eb3290774127d6b98.jpg",
"images/file3.jpg": "d6b98127162969a0808f3eb32907744d.jpg"
}
```
## Compatibility
This plugin is compatible with Webpack 1.x and 2.x.
## Integrations
### Ruby on Rails
Requiring assets in Rails will be a bit different and needs some configuration. Read our [Rails helper documentation](documentation/integrations/rails.md).
### Others
We're open for pull requests that add instructions about how to integrate this plugin with other frameworks.
## License
The MIT License
 © 2016 Infinum Inc.