Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Juho Vepsäläinen
    @bebraw
    i also had a chance to play with webhooks
    Artem Sapegin
    @sapegin
    They feel too close.
    Juho Vepsäläinen
    @bebraw
    npm webhooks are a good addition
    there's a little tool for managing them
    so you can subscribe to package publications and so on
    Artem Sapegin
    @sapegin
    Awesome! I know nothing about that.
    Juho Vepsäläinen
    @bebraw
    that's how React Finland renders
    Artem Sapegin
    @sapegin
    Nice! I guess I should use that to update the docs on Styleguidist site.
    Juho Vepsäläinen
    @bebraw
    the API contains a webhook that triggers when i push content
    Artem Sapegin
    @sapegin
    And not fetch them from master all the time.
    Juho Vepsäläinen
    @bebraw
    then it restarts and does npm update
    thanks to semver it gets the new content
    then it triggers netlify build (another hook)
    so if i edit site content through github ui, it should go through these
    you could do this for docs etc.
    super nice way to manage
    Artem Sapegin
    @sapegin
    Cool! Once you write a chapter for the book I can try it ;-)
    Juho Vepsäläinen
    @bebraw
    yeah
    it fits well
    Artem Sapegin
    @sapegin
    Juho Vepsäläinen
    @bebraw
    :+1:
    @bebraw i've never used, nor heard, of npm-ci. i think yarn is too far in the lead for a little bit of speed to make people care about another manager - i'd almost take yarn over npm installs simply because of the better illustrated install progress. but i prefer the quick-start of npm-init -y -> write-my-code
    but i have used this a couple of times now: npm-check (checks for unused dependencies)
    Marc G.
    @Mouvedia
    Hello, I think you should add one line to talk about the runner ups and deprecated alternatives to npm in the intro about packages.
    Component and Bower comes to mind.
    Also another sentence about stuff like jspm, duojs, yarn and pnpm wouldn't hurt.
    Marc G.
    @Mouvedia
    In the UMD chapter you could link to https://github.com/LeeCheneler/umd-generator
    Marc G.
    @Mouvedia
    You should link to keepachangelog in the changelog chapter.
    Juho Vepsäläinen
    @bebraw
    :+1: can you open issue(s)? easier to keep track of things
    basically the book was in hold for most of the year due to other business (paid work) but i may be able to free some time in the Fall
    Marc G.
    @Mouvedia
    I am not that passionate to open issues :)
    just wanted to help you out
    Juho Vepsäläinen
    @bebraw
    @Mouvedia no worries. i will set them up :+1:
    Juho Vepsäläinen
    @bebraw
    @Mouvedia survivejs/maintenance-book#85 . maybe comment there (or here and i'll gather)
    i have a long personal list of things to add/change too
    i thought about changing the book so that you can see legacy/modern option
    if you go with only modern, you don't have to worry about things like dist bundles anymore and the problem of packaging becomes much simpler
    another dimension might be perspectives (maintainer, user, ???)
    Artem Sapegin
    @sapegin

    I guess we only cover maintainer perspective now ;-)

    And the modern option: how useful it would be in the real world? I’d focus on techniques we can actually use now.

    Juho Vepsäläinen
    @bebraw
    that's a good question. what i mean is that as a maintainer i wouldn't bother maintaining standalone UMD dist bundle anymore
    i see UMD as legacy
    if we did the book right, it would help product people too
    Artem Sapegin
    @sapegin
    I mean it is legacy if we can avoid it without excluding a big portion of users.
    Artem Sapegin
    @sapegin
    I’ve added a link to Keep a changelog ;-)
    Juho Vepsäläinen
    @bebraw
    :+1:
    Tmoilkonline
    @zyead
    ?
    ..
    Juho Vepsäläinen
    @bebraw
    hey