parcel-transformer-elm-svg-modules
v1.0.6
Published
Elm and SVGs are both awesome. Luckily parcel can help us turn SVG straight into an Elm module.
Downloads
3,074
Readme
Have parcel turn svg into elm modules for you
Elm and SVGs are both awesome. Luckily parcel can help us turn SVG straight into an Elm module.
This plugin is for ParcelJS 📦 version 2
Installing and Setup
npm i -D parcel-transformer-elm-svg-modules
Then in your .parcelrc
add the transformer BEFORE the regular Elm transform
(the svg modules need to be generated before Elm is compiled)
{
"extends": "@parcel/config-default",
"transformers": {
"*.elm": ["parcel-transformer-elm-svg-modules", "..."] // <-- add the new transform here, the "..." is important to keep the other defaults
}
}
Configuration
To configure, add this to your package.json
.
The following entry would load SVGs from src/assets/images/
and combine them into an Elm Module named Icons
located at
src/Icons.elm
.
You can add more entries to the array to generate multiple modules.
Here's an example:
"elmSvgModules": [
{
"inputSvgs": "src/assets/images/svg/*.svg", // a glob pattern to place where your SVGs are
"outputModuleName": "Icons", // the module name of the Elm module that will be generated
"outputModuleDir": "src" // the location where Elm module will be generated
}
],
| Option | Required | Default | | ------ | ------- | ------- | | inputSvgs | Yes | - | | outputModuleName | No | Icons | | outputModuleDir | no | src |
outputModuleName
can also be something like Acme.Icons
to generate a nested
module. Together with outputModuleDir
of src
the final module will be at
src/Acme/Icons.elm
(using \
on Windows)
Using the new Module in your code
Make sure to add elm/svg
and elm/virtual-dom
to your elm.json
elm install elm/svg
elm install elm/virtual-dom
Then in your Elm use your SVGs by importing the generated module.
-- the imports are named after the original file names of the SVGs
-- burger-menu.svg will result in an burgerMenu function
import Icons (burgerMenu, someOtherIcon)
view model =
div []
[ burgerMenu []
, someOtherIcon []
]
Dealing with the generated file (the recommended way)
It's recommended to put the generated files into the elm-stuff
directory,
where it is likely ignored git by anyway. It works well and you'll never
really see the generated files while coding.
- Set the
outputModuleDir
toelm-stuff/elm-svg-modules
- Add
elm-stuff/elm-svg-modules
to thesource-directories
in your project'selm.json
Dealing with the generated file (the other way)
If for some reason you do not want to have the generated file in elm-stuff
,
you can just put them somewhere else, i.e. your src
folder and add them to
your .gitignore
.
- Set the
outputModuleDir
tosrc
- Add
src/Icons.elm
(or however the file is named in your configuration) to the.gitignore
in your project.
How it works
When the Elm module is processed by parcel this plugin uses its config to find all the svg files and generates one Elm module per item in the config array.
Credits
This plugin uses the awesome svg2elm
package under the hood.
Also lot's of inspiration for this plugin came from this repo, which did the same as a parcel v1 plugin.