home.social

#newnpmmodule — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #newnpmmodule, aggregated by home.social.

fetched live
  1. Released a new CLI tool that builds upon github.com/yoavbls/pretty-ts-e to provide prettified TS errors in the terminal: github.com/voxpelli/pretty-ts-

    It contains an additional party trick in the shape of optionally outputting as markdown, thanks to a new version of my "markdown-or-chalk” module: github.com/voxpelli/markdown-o

    #newNpmModule #npmRelease #typescript #typesInJs #nodejs

  2. Released a new CLI tool that builds upon github.com/yoavbls/pretty-ts-e to provide prettified TS errors in the terminal: github.com/voxpelli/pretty-ts-

    It contains an additional party trick in the shape of optionally outputting as markdown, thanks to a new version of my "markdown-or-chalk” module: github.com/voxpelli/markdown-o

    #newNpmModule #npmRelease #typescript #typesInJs #nodejs

  3. Released a new CLI tool that builds upon github.com/yoavbls/pretty-ts-e to provide prettified TS errors in the terminal: github.com/voxpelli/pretty-ts-

    It contains an additional party trick in the shape of optionally outputting as markdown, thanks to a new version of my "markdown-or-chalk” module: github.com/voxpelli/markdown-o

    #newNpmModule #npmRelease #typescript #typesInJs #nodejs

  4. Released a new CLI tool that builds upon github.com/yoavbls/pretty-ts-e to provide prettified TS errors in the terminal: github.com/voxpelli/pretty-ts-

    It contains an additional party trick in the shape of optionally outputting as markdown, thanks to a new version of my "markdown-or-chalk” module: github.com/voxpelli/markdown-o

    #newNpmModule #npmRelease #typescript #typesInJs #nodejs

  5. Released a new CLI tool that builds upon github.com/yoavbls/pretty-ts-e to provide prettified TS errors in the terminal: github.com/voxpelli/pretty-ts-

    It contains an additional party trick in the shape of optionally outputting as markdown, thanks to a new version of my "markdown-or-chalk” module: github.com/voxpelli/markdown-o

    #newNpmModule #npmRelease #typescript #typesInJs #nodejs

  6. Early release of a new companion module to my "list-installed" module: ”list-dependents”

    It uses npm and optionally @ecosystems to look up the dependents of a module and returns the package.json files of them similar to how "list-installed" do for locally installed modules.

    On top of the package.json data it also returns download metrics as well as some @ecosystems extras.

    github.com/voxpelli/list-depen

    #npmRelease #newNpmModule

  7. Early release of a new companion module to my "list-installed" module: ”list-dependents”

    It uses npm and optionally @ecosystems to look up the dependents of a module and returns the package.json files of them similar to how "list-installed" do for locally installed modules.

    On top of the package.json data it also returns download metrics as well as some @ecosystems extras.

    github.com/voxpelli/list-depen

    #npmRelease #newNpmModule

  8. Early release of a new companion module to my "list-installed" module: ”list-dependents”

    It uses npm and optionally @ecosystems to look up the dependents of a module and returns the package.json files of them similar to how "list-installed" do for locally installed modules.

    On top of the package.json data it also returns download metrics as well as some @ecosystems extras.

    github.com/voxpelli/list-depen

    #npmRelease #newNpmModule

  9. Early release of a new companion module to my "list-installed" module: ”list-dependents”

    It uses npm and optionally @ecosystems to look up the dependents of a module and returns the package.json files of them similar to how "list-installed" do for locally installed modules.

    On top of the package.json data it also returns download metrics as well as some @ecosystems extras.

    github.com/voxpelli/list-depen

    #npmRelease #newNpmModule

  10. Early release of a new companion module to my "list-installed" module: ”list-dependents”

    It uses npm and optionally @ecosystems to look up the dependents of a module and returns the package.json files of them similar to how "list-installed" do for locally installed modules.

    On top of the package.json data it also returns download metrics as well as some @ecosystems extras.

    github.com/voxpelli/list-depen

    #npmRelease #newNpmModule

  11. Forked and revived an old module I made at my previous job:

    ts-ignore-import: npmjs.com/package/ts-ignore-im

    It helps ignoring optional type imports in autogenerated type declarations – which is especially useful when one writes #typesInJs.

    Ignoring an optional type import makes it silently revert to ”any” when the type can not be imported, which is great when one eg. wants to reference multiple frameworks in the same project without requiring all those types.

    #npmRelease #newNpmModule #typescript

  12. Forked and revived an old module I made at my previous job:

    ts-ignore-import: npmjs.com/package/ts-ignore-im

    It helps ignoring optional type imports in autogenerated type declarations – which is especially useful when one writes #typesInJs.

    Ignoring an optional type import makes it silently revert to ”any” when the type can not be imported, which is great when one eg. wants to reference multiple frameworks in the same project without requiring all those types.

    #npmRelease #newNpmModule #typescript

  13. Forked and revived an old module I made at my previous job:

    ts-ignore-import: npmjs.com/package/ts-ignore-im

    It helps ignoring optional type imports in autogenerated type declarations – which is especially useful when one writes #typesInJs.

    Ignoring an optional type import makes it silently revert to ”any” when the type can not be imported, which is great when one eg. wants to reference multiple frameworks in the same project without requiring all those types.

    #npmRelease #newNpmModule #typescript

  14. Forked and revived an old module I made at my previous job:

    ts-ignore-import: npmjs.com/package/ts-ignore-im

    It helps ignoring optional type imports in autogenerated type declarations – which is especially useful when one writes #typesInJs.

    Ignoring an optional type import makes it silently revert to ”any” when the type can not be imported, which is great when one eg. wants to reference multiple frameworks in the same project without requiring all those types.

    #npmRelease #newNpmModule #typescript

  15. Forked and revived an old module I made at my previous job:

    ts-ignore-import: npmjs.com/package/ts-ignore-im

    It helps ignoring optional type imports in autogenerated type declarations – which is especially useful when one writes #typesInJs.

    Ignoring an optional type import makes it silently revert to ”any” when the type can not be imported, which is great when one eg. wants to reference multiple frameworks in the same project without requiring all those types.

    #npmRelease #newNpmModule #typescript

  16. Released early versions of two new npm modules:

    * Umzeption, a module based provider of umzug migrations: github.com/voxpelli/umzeption
    * plugin-importer, recursively imports a plugin tree in order of dependencies: github.com/voxpelli/plugin-imp

    #npmRelease #newNpmModule #NodeJS

  17. Released early versions of two new npm modules:

    * Umzeption, a module based provider of umzug migrations: github.com/voxpelli/umzeption
    * plugin-importer, recursively imports a plugin tree in order of dependencies: github.com/voxpelli/plugin-imp

    #npmRelease #newNpmModule #NodeJS

  18. Released early versions of two new npm modules:

    * Umzeption, a module based provider of umzug migrations: github.com/voxpelli/umzeption
    * plugin-importer, recursively imports a plugin tree in order of dependencies: github.com/voxpelli/plugin-imp

    #npmRelease #newNpmModule #NodeJS

  19. Released early versions of two new npm modules:

    * Umzeption, a module based provider of umzug migrations: github.com/voxpelli/umzeption
    * plugin-importer, recursively imports a plugin tree in order of dependencies: github.com/voxpelli/plugin-imp

    #npmRelease #newNpmModule #NodeJS

  20. Released early versions of two new npm modules:

    * Umzeption, a module based provider of umzug migrations: github.com/voxpelli/umzeption
    * plugin-importer, recursively imports a plugin tree in order of dependencies: github.com/voxpelli/plugin-imp

    #npmRelease #newNpmModule #NodeJS

  21. @mcollina #npmRelease #fastify (adding hashtags makes it easier to follow, and so far I'm the only one using #npmRelease, would be nice to get some traction for such a one as I would love to find releases from people I don't yet follow here. That and #newNpmModule for any new modules)

  22. @mcollina #npmRelease #fastify (adding hashtags makes it easier to follow, and so far I'm the only one using #npmRelease, would be nice to get some traction for such a one as I would love to find releases from people I don't yet follow here. That and #newNpmModule for any new modules)

  23. @mcollina #npmRelease #fastify (adding hashtags makes it easier to follow, and so far I'm the only one using #npmRelease, would be nice to get some traction for such a one as I would love to find releases from people I don't yet follow here. That and #newNpmModule for any new modules)

  24. @mcollina #npmRelease #fastify (adding hashtags makes it easier to follow, and so far I'm the only one using #npmRelease, would be nice to get some traction for such a one as I would love to find releases from people I don't yet follow here. That and #newNpmModule for any new modules)

  25. @mcollina #npmRelease #fastify (adding hashtags makes it easier to follow, and so far I'm the only one using #npmRelease, would be nice to get some traction for such a one as I would love to find releases from people I don't yet follow here. That and #newNpmModule for any new modules)

  26. Started using `node:test` in some of my projects but was missing the reporter style that I'm used to from Mocha, so I decided to fix that: github.com/voxpelli/node-test-

    #npmRelease #NodeJS #nodeTest #newNpmModule

  27. Started using `node:test` in some of my projects but was missing the reporter style that I'm used to from Mocha, so I decided to fix that: github.com/voxpelli/node-test-

    #npmRelease #NodeJS #nodeTest #newNpmModule

  28. Started using `node:test` in some of my projects but was missing the reporter style that I'm used to from Mocha, so I decided to fix that: github.com/voxpelli/node-test-

    #npmRelease #NodeJS #nodeTest #newNpmModule

  29. Started using `node:test` in some of my projects but was missing the reporter style that I'm used to from Mocha, so I decided to fix that: github.com/voxpelli/node-test-

    #npmRelease #NodeJS #nodeTest #newNpmModule

  30. Started using `node:test` in some of my projects but was missing the reporter style that I'm used to from Mocha, so I decided to fix that: github.com/voxpelli/node-test-

    #npmRelease #NodeJS #nodeTest #newNpmModule

  31. Released a new module, a tiny little extension for helping with Chai assertion of non-posix paths: github.com/voxpelli/chai-posix

    #npm #npmRelease #newNpmModule #chaijs

  32. Released a new module, a tiny little extension for helping with Chai assertion of non-posix paths: github.com/voxpelli/chai-posix

    #npm #npmRelease #newNpmModule #chaijs

  33. Released a new module, a tiny little extension for helping with Chai assertion of non-posix paths: github.com/voxpelli/chai-posix

    #npm #npmRelease #newNpmModule #chaijs

  34. Released a new module, a tiny little extension for helping with Chai assertion of non-posix paths: github.com/voxpelli/chai-posix

    #npm #npmRelease #newNpmModule #chaijs

  35. Released a new module, a tiny little extension for helping with Chai assertion of non-posix paths: github.com/voxpelli/chai-posix

    #npm #npmRelease #newNpmModule #chaijs