Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 28 20:20
    EisenbergEffect review_request_removed #888
  • Jan 25 22:47
    hiaux0 opened #174
  • Jan 25 22:46
    hiaux0 edited #173
  • Jan 24 11:16
    hiaux0 labeled #173
  • Jan 24 11:15
    hiaux0 opened #173
  • Jan 24 01:35
    khalbbaz opened #72
  • Jan 23 22:26
    3cp closed #1189
  • Jan 23 22:26
    3cp labeled #1189
  • Jan 23 22:25
    3cp closed #1192
  • Jan 22 23:44
    3cp closed #1195
  • Jan 22 23:44
    3cp commented #1195
  • Jan 22 09:53

    dependabot[bot] on npm_and_yarn

    (compare)

  • Jan 22 09:53
    dependabot[bot] closed #324
  • Jan 22 09:53
    dependabot[bot] commented #324
  • Jan 22 09:53
    dependabot[bot] labeled #366
  • Jan 22 09:53
    dependabot[bot] opened #366
  • Jan 22 09:53

    dependabot[bot] on npm_and_yarn

    chore(deps): bump node-fetch fr… (compare)

  • Jan 21 20:06
    dependabot[bot] labeled #365
  • Jan 21 20:06
    dependabot[bot] opened #365
  • Jan 21 20:06

    dependabot[bot] on npm_and_yarn

    chore(deps): bump log4js from 0… (compare)

Roland Quast
@rquast
yep
:\
José A. Sachs
@jhewt
Dang
Roland Quast
@rquast
actually
I think it may not
but does by default
and I can't get it to play nice with webpack
nope.. still requires jquery Semantic-Org/Semantic-UI#1175
José A. Sachs
@jhewt
with Aurelia sometimes can be a pain in the ass to work with jQuery
With any framework tbh
Roland Quast
@rquast
yup.. rather not include it if I didn't have to
lot of animation stuff in it that people use (like semantic)
José A. Sachs
@jhewt
and things like pickdates and so on, sadly there's almost no css framework with no dependencies
That's why I use Material Design Lite, I can call the element's methods with Aurelia's html references
Max
@MaximBalaganskiy
is jquery problem only webpack specific?
Tomas Billborn
@tomasbillborn
Is there no support for {less} with easy-webpack?
Roland Quast
@rquast
@MaximBalaganskiy I don't have a problem with jquery and webpack.. just semantic - Semantic-Org/Semantic-UI#3533
I'd kill for a nice ui that just works.
José A. Sachs
@jhewt
MDL works just fine for me
or Polymer
Roland Quast
@rquast
I used mdl before semantic
José A. Sachs
@jhewt
ah
Roland Quast
@rquast
mdl didn't have enough for what I needed
semantic has all the features, but not webpack friendly
José A. Sachs
@jhewt
Indeed, "lite"
Dwayne Charrington
@Vheissu
@tomasbillborn I created a Sass one which hasn't been released yet, planning on getting to a Stylus and Less one tonight probably.
Also wanting to add in support for Autoprefixer as well.
Tomas Billborn
@tomasbillborn
Thats great, I would actually rather just go webpack as it is, but documentation on how to actually implement it feel like it is minimal atm
Dwayne Charrington
@Vheissu
That's the great thing about what @niieani started with Easy Webpack, lots of configurations for Webpack projects without needing to pull your hair out. Webpack has quite a steep learning curve when you start getting knee-deep into it.
Roland Quast
@rquast
that new skeleton looks pretty good
Tomas Billborn
@tomasbillborn
Well I had no problem before this release, I think some parts of it seem great, but I rather have a "normal" implementation of webpack
Roland Quast
@rquast
easy webpack a great idea
Tomas Billborn
@tomasbillborn
If I would need to implement a { less } loader its there, I dont wanna have to hack into the setup and have "some easy-webpack" and some regular webpack
Dwayne Charrington
@Vheissu
You can define your own loaders inside of the config without using Easy Webpack as well.
Until my copy files plugin contribution is released I have this:
      (function() {
        return {
          plugins: [
            new CopyWebpackPlugin([{
              from: 'src/assets/images',
              to: 'images'
            }])
          ]
        }
      })()
Tomas Billborn
@tomasbillborn
Well then we are back to minimal documenation and me sitting and reading your repo code : )
Roland Quast
@rquast
I don't think anything is easy when it comes to build scripts... webpack included
Dwayne Charrington
@Vheissu
This is my Sass one (still not perfect though, CSS is still inlined):
      (function () {
        const extractCss = { filename: '[name].css', allChunks: false, sourceMap: false };
        const extractCSSinstance = extractCss ? new ExtractTextPlugin(extractCss.filename || '[name].css', extractCss) : null;

        let config = {
          module: {
            loaders: get(this, 'module.loaders', []).concat([{
              test: /\.scss$/i,
              loaders: extractCss ? extractCSSinstance.extract('style', ['css', 'postcss', 'sass']) : ['style', 'css', 'postcss', 'sass']
            }])
          }
        };

        return config;
      })(),
Roland Quast
@rquast
but that easy webpack should be good at least for a template of how things are done
and you can fork if you want to keep track of changes
Tomas Billborn
@tomasbillborn
I appreciate your help and what you are doing, but I am having a hardtime to see why I need to reinvent the wheel, there is a loader for less and webpack already
Dwayne Charrington
@Vheissu
Easy Webpack doesn't change anything, the syntax for defining loaders and whatnot remains the same. You just use it within the confines of the plugin now.
Tomas Billborn
@tomasbillborn
With this i have to write an extra config for each loader
Dwayne Charrington
@Vheissu
The above is no different than how you normally define a loader. The one difference being you register it with the generateConfig function. The configs are just wrapped in functions now.
Roland Quast
@rquast
I dunno.. easy-webpack makes a lot of sense to me. It's not reinventing the wheel if it consolidates config that can normally be spread across a webpack config file.
maybe it's just inappropriately named.. maybe should be something like "cleanly-organised-webpack".
Tomas Billborn
@tomasbillborn
Before I had simply to define the less loader in the module.loader for it to work now I have to define it through a function or a new file exporting a module. Not saying easy-webpack is bad because I havent evaluated it enough, simply I think it hads complexity
adds*
Hopefully I am proven wrong, atm it just not super clear how to do things that before could be implemented pretty easy
Roland Quast
@rquast
to me it looks similar to what you get in configuration files for apache etc... all broken up into configuration parts