package
Webpack loader to handle browserify transforms as intended
npm install ify-loaderGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
Tagged topics.
Webpack loader to handle browserify transforms as intended.
Install the loader using npm:
npm install --save ify-loaderYou can then update your webpack.config.js in a similar fashion to the following to add browserify transform support to your project's dependencies:
module.exports = {
module: {
loaders: [
// This applies the loader to all of your dependencies,
// and not any of the source files in your project:
{
test: /node_modules/,
loader: 'ify-loader'
}
]
}
}Note that you're also free to apply this loader to files in your own project. Include the following in your project's webpack.config.js:
module.exports = {
module: {
loaders: [
// support local package.json browserify config
{
test: /\.js$/,
loader: 'ify-loader',
enforce: 'post'
}
]
}
}Any browserify transforms you include in package.json will get picked up and applied this way:
{
"name": "my-project",
"dependencies": {
"glslify": "5.0.0",
"brfs": "1.4.2"
},
"browserify": {
"transform": [
"glslify",
"brfs"
]
}
}When given the choice, I lean more in favour of browserify for its simplicity and compatability with node.js — however from time to time I need to work on projects that use webpack. The thing I run into issues with most often when switching between the two is the difference in how webpack handles source transforms compared to browserify.
Webpack provides you with a "global" configuration where you specify how your project and its dependencies are transformed in a single place. Browserify, however, scopes transforms to the current package to avoid conflicts between different dependencies' sources using the browserify.transform property in package.json.
There are pros and cons to both approaches — Webpack gives you more control, at the expense of having to configure each transform used in your dependency tree. Unlike transform-loader, ify-loader will automatically determine which browserify transforms to apply to your dependencies for you the same way that browserify itself does, making the process a lot more bearable in complex projects!
MIT, see LICENSE.md for details.
gkatsev
me@gkatsev.com
maxogden
max@maxogden.com
thlorenz
thlorenz10@gmail.com
terinjokes
terinjokes@gmail.com
jmm
npm-public@jessemccarthy.net
mellowmelon
palmermebane@gmail.com
ashaffer88
darawk@gmail.com
balupton
b@lupton.cc
cwmma
calvin.metcalf@gmail.com
jprichardson
jprichardson@gmail.com
indutny
blackhole@livebox.sh
jryans
jryans@gmail.com
sethvincent
sethvincent@gmail.com
yoshuawuyts
javascript@yosh.is
ungoldman
ungoldman@gmail.com
ahdinosaur
michael.williams@enspiral.com
elnounch
contact@elnounch.net
parshap
parshap+npm@gmail.com
yerkopalma
yerko.palma@usach.cl
forbeslindesay
forbes@lindesay.co.uk
leichtgewicht
martin.heidegger@gmail.com
garann
garann@gmail.com
bret
bcomnes@gmail.com
anandthakker
vestibule@anandthakker.net
mattdesl
dave.des@gmail.com
hughsk
hughskennedy@gmail.com
fpereira1
pereira.filype@gmail.com
goto-bus-stop
renee@kooi.me
bpostlethwaite
post.ben.here@gmail.com
emilbayes
github@tixz.dk
stevemao
maochenyan@gmail.com
pkrumins
peteris.krumins@gmail.com
tehshrike
me@JoshDuff.com
defunctzombie
shtylman@gmail.com
lukechilds
lukechilds123@gmail.com
raynos
raynos2@gmail.com
etpinard
code@etpinard.xyz
Estimated unpacked size across 32 packages.
4.2 MB
Includes dependencies.
7 direct · 3 outdated
^1.0.0
7.0.15
^0.1.5
0.1.5
^1.1.6
1.22.14
0.0.1
0.0.1
^0.3.0
4.0.0
0.0.4
0.0.4
^2.0.2
7.0.1