Feature/readme update
Configuration for Webpack 4.
Codecov Report
Merging #85 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #85 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 45 45
=====================================
Hits 45 45
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 716a0d6...6095f61. Read the comment docs.
Codecov Report
Merging #85 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #85 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 45 45
=====================================
Hits 45 45
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 716a0d6...6095f61. Read the comment docs.
Codecov Report
Merging #85 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #85 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 45 45
=====================================
Hits 45 45
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 776bd43...f8a2244. Read the comment docs.
Thanks for your pull request, looks good to me, @sn3p any thoughts?
@SzymonKrysztofiak thanks for the PR 💯 Will look into it today
No problem, btw. this is very good lib, and if You have any suggestions to this PR, i'll find time to look at this again :)
Thanks for sharing your implementation. I really like the path aliases :)
We are in the process of moving from Brunch to Webpack in our apps. Our approach is slightly different, but I guess the result is the same (?). We are kinda new to Webpack so I'm not sure if we are on the right track.
I'm curious, would you prefer one implementation over the other?
assets/webpack.config.js
const glob = require("glob");
module.exports = {
entry: {
app: [].concat(
glob.sync("./js/**/*.js"),
glob.sync("../lib/app_web/cells/**/*.js"),
glob.sync("../lib/app_web/views/**/*.js"),
glob.sync("./css/app.css"),
glob.sync("../lib/app_web/cells/**/*.css"),
glob.sync("../lib/app_web/views/**/*.css")
)
}
}
assets/js/app.js
import { Builder as CellBuilder } from "@defacto/cell-js";
CellBuilder.reload();
lib/app_web/cells/avatar/index.js
import { Cell, Builder } from "@defacto/cell-js";
class AvatarCell extends Cell {
initialize() {}
}
Builder.register(AvatarCell, "AvatarCell");
export default AvatarCell;
We are kinda new to Webpack so I'm not sure if we are on the right track.
I'm saying this because we are experiencing some issues with our implementation of CSS Modules (see this post on StackOverflow).
Are you using CSS Modules by any chance?
Unfortunately, I don't work with CSS-Modules.
Maybe @TheLarkInn will be able to help, he is an expert from Webpack.
Unfortunately, I don't work with CSS-Modules.
Maybe @TheLarkInn will be able to help, he is an expert from Webpack
Any help or advise is welcome 👍