Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Andy Wermke
    @andywer
    Awesome!
    Suggestion: Add a screenshot to the readme, like one of those you put in the issue
    Artem Sapegin
    @sapegin
    Sure, I will ;-)
    Artem Sapegin
    @sapegin
    Done ;-)
    Andy Wermke
    @andywer
    btw, the migration guide made good progress https://gist.github.com/andywer/65435f72b159c166cbb14d9e1d4e5dd4
    Artem Sapegin
    @sapegin
    Cool, I’ll have a look after lunch.
    Vlad Zhukov
    @vlad-zhukov
    @andywer thanks for an invitation! 🎉
    This code snippet won't work :smile: https://gist.github.com/andywer/65435f72b159c166cbb14d9e1d4e5dd4#resolve-instead-of-resolvealiases
    Andy Wermke
    @andywer
    Ooops. Thanks, Vlad!
    Artem Sapegin
    @sapegin

    though, in order to not break compatibility too much

    What do you mean by this?

    webpack-blocks package

    It also contains all the utility functions.

    babel-core is now a peer dependency of the babel block

    And webpack-blocks package too even if you use TypeScript ;-|

    “Migration is trivial:” → “” ;-)

    If you feel like this is a feature you really want to have, open an issue

    We’ve just closed all of them ;-)

    We officially support webpack 3 now 🎉

    And don’t support webpack 1.

    Artem Sapegin
    @sapegin
    I think it’s ready to be used in webpack-blocks: https://github.com/sapegin/q-i
    Andy Wermke
    @andywer
    cool!
    Andy Wermke
    @andywer
    Will open a PR to add the migration guide today. Anything else left to do before 1.0 RC release?
    Artem Sapegin
    @sapegin
    Awesome!
    Artem Sapegin
    @sapegin
    We have four unmerged PRs.
    Vlad Zhukov
    @vlad-zhukov
    Can someone merge my refactor PR if it's ok? Would like to do some more
    @andywer Thanks!
    Andy Wermke
    @andywer
    Sure thing =)
    Vlad Zhukov
    @vlad-zhukov
    I am going to remove fileTypes entirely, what do you think?
    Andy Wermke
    @andywer
    I wouldn't hurry too much. We have enough breaking changes for now 😅
    Artem Sapegin
    @sapegin
    Highly recommend to check docs: https://github.com/sapegin/textlint-rule-terminology ;-)
    Vlad Zhukov
    @vlad-zhukov
    I need a css block w/o style-loader, should I create a PR with such option for the css block?
    Andy Wermke
    @andywer
    Sure. Just out of curiosity... What's the use case? :)
    Vlad Zhukov
    @vlad-zhukov
    There are few actually, one is obvious when you want to output it into a file
    the other one if you want to load css as a string inside of a bundle
    css-loader has a toString method
    Jan van Brügge
    @jvanbruegge
    the first one can be accomplished by thr extract text plugin
    Vlad Zhukov
    @vlad-zhukov
    I know but I dislike it
    Artem Sapegin
    @sapegin
    Nobody likes it ;-)
    Vlad Zhukov
    @vlad-zhukov
    file-loader + extract-loader work much better
    Artem Sapegin
    @sapegin
    Should we merge this? andywer/webpack-blocks#216
    Artem Sapegin
    @sapegin
    Last thing that still bothers me in 1.0 is that extract text plugin deprecation warning.
    Andy Wermke
    @andywer
    Yeah, the deprecation messages are annoying, but not necessarily a blocker
    Artem Sapegin
    @sapegin
    I’d suggest to get rid of webpack 2 ;-)
    Andy Wermke
    @andywer
    i opened an issue in the extract-text-plugin repo, but something was blocking
    Artem Sapegin
    @sapegin
    From their side?
    Andy Wermke
    @andywer
    here it is: https://github.com/webpack-contrib/extract-text-webpack-plugin/issues/567#issuecomment-322865069
    they said the webpack@2 version is not compatible with webpack@3 and i needed to check back with you, since i haven't tried and am lacking the time to investigate myself
    Artem Sapegin
    @sapegin
    Wrote a comment there. But it may be to late. There’s not much sense to support webpack 2 as much as I can see.
    Andy Wermke
    @andywer
    Yeah, probably
    Thx for your efforts 😊
    Artem Sapegin
    @sapegin
    They’ve answered. And it means we don’t support webpack 3 ;-|
    Andy Wermke
    @andywer
    Yeah, I saw it. Well, then let's rather have two major versions of extract-text, one for webpack v2 and one for v3 and ship the v3-compatible version with the unscoped webpack-blocks package
    Artem Sapegin
    @sapegin
    Sounds good!
    Artem Sapegin
    @sapegin
    How can I help with that?
    Artem Sapegin
    @sapegin
    Here it is: andywer/webpack-blocks#225
    Work in progress, need some feedback ;-)
    Anyone have any feedback for this PR by @vlad-zhukov? Looks good to me.
    andywer/webpack-blocks#224