The easiest way to publish an npm package? (2024)

แชร์
ฝัง
  • เผยแพร่เมื่อ 5 ม.ค. 2025

ความคิดเห็น •

  • @JoshuaMorony
    @JoshuaMorony  4 หลายเดือนก่อน +1

    Next newsletter goes out tomorrow with some extra notes on TypeScript mixins: mobirony.ck.page/4a331b9076

  • @uquantum
    @uquantum หลายเดือนก่อน

    thanks so much!

  • @kocram
    @kocram 4 หลายเดือนก่อน +2

    Thanks for the video! To be honest, I don't find 'npm publish' that complicated. I guess adding an additional layer with Nx introduces more things to manage, don't you think? Also, while there aren't too many fans of "npm link" out there, I'm one of them 😂. It's a great solution for all npm-based frameworks, and I wish more people talked about it since libraries are everywhere. Great content, by the way!

    • @JoshuaMorony
      @JoshuaMorony  4 หลายเดือนก่อน +2

      You still have to 'npm publish' with Nx anyway, the tricky part it handles is the out of the box compilation to both CJS and ESM, auto generating the package.json entries for that, and if you need them it can also handle adding secondary entry points for you.

  • @danielwahrscheinlich
    @danielwahrscheinlich 4 หลายเดือนก่อน +1

    Can you show how to integrate:
    Husky, Commitlint, Commitizen, Automatic Semver with ci/cd/github workflow (with eg jscutlery/semver package), auto distribution.. and so on

    • @NatoBoram
      @NatoBoram 4 หลายเดือนก่อน

      You just have to go to their website, read the on-screen instructions and it should be done pretty easily

    • @danielwahrscheinlich
      @danielwahrscheinlich 4 หลายเดือนก่อน +1

      @@NatoBoram yeah would be nice to have a video about it too to spread awareness.

    • @GuillermoArellano
      @GuillermoArellano 4 หลายเดือนก่อน +1

      These additional tools should be automatically invoiced by the CLI generator at this point.

  • @mortezatourani7772
    @mortezatourani7772 4 หลายเดือนก่อน

    Another way to bump and create tag at the same time:
    yarn version [--(major|minor|patch|...)]

  • @DirkLuijk
    @DirkLuijk 4 หลายเดือนก่อน

    Personally I think everyone should move away from CommonJS and fully embrace ESM. It's a native cross-runtime standard that works everywhere.