-
-
Notifications
You must be signed in to change notification settings - Fork 23
brfs not inlining... what am I missing? #3
Comments
You need to change your configuration to: {
test: /\.js$/,
loader: "transform?brfs"
} The brfs transform should process the JS file. The test is executed on the absolute filename. But this makes all javascript files uncachable, which has a big performance impact in watch mode. So you should better use |
Ah, got it thanks. So this makes the browserify loader enabled for all Also, using
|
Yep, and this is the problem here. It tries to use the specified loader But the real solution is to restrict the loader configuration to your app code. {
test: /\.js$/,
include: path.join(__dirname, "lib"),
loader: "transform?brfs"
} |
Could you add this ( |
I'm using brfs and would like to restrict what dirs are included. However, this syntax isn't working for me. include: path.join(__dirname, "lib"), I've tried hard coding the absolute path and it still wouldn't process the files in the dir. Any suggestions? |
Still meet the same problem here.
And my code is
|
Here is the file:
The above works fine with browserify:
browserify index.js -t brfs > bundle.js
But I can't get it to work with webpack. Here is my config:
Running it through webpack leads to the following wrapped inside the bootstrap:
I changed it to use
__dirname
which seems to affect the build:And now the bundled output from webpack reads:
Still, the file is not being inlined into the bundle like it is with brfs / browserify.
The text was updated successfully, but these errors were encountered: