#npmrelease — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #npmrelease, aggregated by home.social.
-
New #npmRelease for #neostandard: github.com/neostandard/... Highlights: - With the addition of eslint-plugin-import-x all the rules from StandardJS have now been added and we are pretty much ready to release 1.0.0 - Pinned stylistic to avoid a recent regression in stylistic/indent
Release v0.12.0 · neostandard/... -
Anyone who have experienced issues with #typescriptEslint on the latest #ESLint releases when using #neostandard: Update to #npmRelease 0.11.9 to get the latest typescript-eslint: https://github.com/neostandard/neostandard/releases/tag/v0.11.9
-
My PR supporting #graphql_tag style queries got merged and released in #mercurius 5.0.0!
This enables easier handling of fragments in #graphql, and I decided to follow up with a real world example in the PR post release to aid as a future reference for people: https://github.com/mercurius-js/mercurius/pull/1108#issuecomment-2362986609
Thanks for the merge @mcollina 🙏
-
Since a lot of people are relying on standard I also made an exception and did a patch #npmRelease of that, 17.1.1, to pin the #eslintPluginReact dependency.
Doing no new development at standard but when I can help a lot of users easily then I of course will.
-
Since a lot of people are relying on standard I also made an exception and did a patch #npmRelease of that, 17.1.1, to pin the #eslintPluginReact dependency.
Doing no new development at standard but when I can help a lot of users easily then I of course will.
-
Since a lot of people are relying on standard I also made an exception and did a patch #npmRelease of that, 17.1.1, to pin the #eslintPluginReact dependency.
Doing no new development at standard but when I can help a lot of users easily then I of course will.
-
Since a lot of people are relying on standard I also made an exception and did a patch #npmRelease of that, 17.1.1, to pin the #eslintPluginReact dependency.
Doing no new development at standard but when I can help a lot of users easily then I of course will.
-
Since a lot of people are relying on standard I also made an exception and did a patch #npmRelease of that, 17.1.1, to pin the #eslintPluginReact dependency.
Doing no new development at standard but when I can help a lot of users easily then I of course will.
-
In other #npmRelease news:
The new v0.11.5 version of #neostandard contains a tweak that disables jsx rules on all ordinary js/ts files – maybe providing some better performance but mostly avoiding bugs like the one that currently plagues latest version of #eslintPluginReact
https://github.com/neostandard/neostandard/releases/tag/v0.11.5
-
In other #npmRelease news:
The new v0.11.5 version of #neostandard contains a tweak that disables jsx rules on all ordinary js/ts files – maybe providing some better performance but mostly avoiding bugs like the one that currently plagues latest version of #eslintPluginReact
https://github.com/neostandard/neostandard/releases/tag/v0.11.5
-
In other #npmRelease news:
The new v0.11.5 version of #neostandard contains a tweak that disables jsx rules on all ordinary js/ts files – maybe providing some better performance but mostly avoiding bugs like the one that currently plagues latest version of #eslintPluginReact
https://github.com/neostandard/neostandard/releases/tag/v0.11.5
-
In other #npmRelease news:
The new v0.11.5 version of #neostandard contains a tweak that disables jsx rules on all ordinary js/ts files – maybe providing some better performance but mostly avoiding bugs like the one that currently plagues latest version of #eslintPluginReact
https://github.com/neostandard/neostandard/releases/tag/v0.11.5
-
In other #npmRelease news:
The new v0.11.5 version of #neostandard contains a tweak that disables jsx rules on all ordinary js/ts files – maybe providing some better performance but mostly avoiding bugs like the one that currently plagues latest version of #eslintPluginReact
https://github.com/neostandard/neostandard/releases/tag/v0.11.5
-
Released a new CLI tool that builds upon https://github.com/yoavbls/pretty-ts-errors to provide prettified TS errors in the terminal: https://github.com/voxpelli/pretty-ts-errors-cli
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: https://github.com/voxpelli/markdown-or-chalk
-
If some of you are testing the new #neostandard successor to #standardjs, then give me a ping and tell me how it went!
#npmRelease #newNpmModule #eslint #eslint9 #semistandard #nodejs #javascript #typescript
https://github.com/neostandard/neostandard
https://mastodon.social/@voxpelli/112525896276661651 -
If some of you are testing the new #neostandard successor to #standardjs, then give me a ping and tell me how it went!
#npmRelease #newNpmModule #eslint #eslint9 #semistandard #nodejs #javascript #typescript
https://github.com/neostandard/neostandard
https://mastodon.social/@voxpelli/112525896276661651 -
If some of you are testing the new #neostandard successor to #standardjs, then give me a ping and tell me how it went!
#npmRelease #newNpmModule #eslint #eslint9 #semistandard #nodejs #javascript #typescript
https://github.com/neostandard/neostandard
https://mastodon.social/@voxpelli/112525896276661651 -
If some of you are testing the new #neostandard successor to #standardjs, then give me a ping and tell me how it went!
#npmRelease #newNpmModule #eslint #eslint9 #semistandard #nodejs #javascript #typescript
https://github.com/neostandard/neostandard
https://mastodon.social/@voxpelli/112525896276661651 -
If some of you are testing the new #neostandard successor to #standardjs, then give me a ping and tell me how it went!
#npmRelease #newNpmModule #eslint #eslint9 #semistandard #nodejs #javascript #typescript
https://github.com/neostandard/neostandard
https://mastodon.social/@voxpelli/112525896276661651 -
Published a new version of my "buffered-async-iterable" module: https://github.com/voxpelli/buffered-async-iterable/releases/tag/v1.0.0
It can now return the result in order (at cost of performance of course) and it also got a new method: mergeIterables(), which interweaves values from multiple async iterables in parallel
-
Published a new version of my "buffered-async-iterable" module: https://github.com/voxpelli/buffered-async-iterable/releases/tag/v1.0.0
It can now return the result in order (at cost of performance of course) and it also got a new method: mergeIterables(), which interweaves values from multiple async iterables in parallel
-
Published a new version of my "buffered-async-iterable" module: https://github.com/voxpelli/buffered-async-iterable/releases/tag/v1.0.0
It can now return the result in order (at cost of performance of course) and it also got a new method: mergeIterables(), which interweaves values from multiple async iterables in parallel
-
Published a new version of my "buffered-async-iterable" module: https://github.com/voxpelli/buffered-async-iterable/releases/tag/v1.0.0
It can now return the result in order (at cost of performance of course) and it also got a new method: mergeIterables(), which interweaves values from multiple async iterables in parallel
-
Published a new version of my "buffered-async-iterable" module: https://github.com/voxpelli/buffered-async-iterable/releases/tag/v1.0.0
It can now return the result in order (at cost of performance of course) and it also got a new method: mergeIterables(), which interweaves values from multiple async iterables in parallel
-
Released a couple of improvements to installed-check these last few days:
- pnpm workspace support
- symlink supportAnd right now added to that list with:
- autofixing support
#npmRelease https://fosstodon.org/@webpro/112218193414017573
-
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.
-
Forked and revived an old module I made at my previous job:
ts-ignore-import: https://www.npmjs.com/package/ts-ignore-import
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.
-
Did my first #npmRelease of #MochaJS. Version 10.4.0 is now available, including some features and some fixes: https://github.com/mochajs/mocha/releases/tag/v10.4.0
Great collaboration with @JoshuaKGoldberg and @uzlopak as well as with the individual contributors.
Next up I hope to pick up the pace of my contributions on this project, but first I have some standard linting to enhance :BlobhajHeart:
-
Released a new major version of my npm engine range validator – now also supports peerDependency range validation and supports running on workspaces.
To ensure you don’t promise more than your dependencies can deliver, start using “installed-check” 9.0.0 now: https://github.com/voxpelli/node-installed-check/releases/tag/v9.0.0
#npmRelease #linting #npm #npmWorkspace #peerDependencies #packageJson #nodeModules
-
Released early versions of two new npm modules:
* Umzeption, a module based provider of umzug migrations: https://github.com/voxpelli/umzeption
* plugin-importer, recursively imports a plugin tree in order of dependencies: https://github.com/voxpelli/plugin-importer -
@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)
-
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: https://github.com/voxpelli/node-test-pretty-reporter
-
Released a new module, a tiny little extension for helping with Chai assertion of non-posix paths: https://github.com/voxpelli/chai-posix-path
-
Stepped in these last few days and did some long overdue releases of #StandardJS despite having lots of else on my plate currently.
New releases of:
- https://github.com/standard/standard-engine/releases/tag/v15.1.0 (First in three quarters!)
- https://github.com/standard/eslint-config-standard/releases/tag/v17.1.0 (First in a year!)
- https://github.com/standard/standard/releases/tag/v17.1.0 (First in a year!)
- https://github.com/standard/semistandard/releases/tag/v17.0.0 (First 17.x release, first release in almost 2 years!)If you like what I do, consider sponsoring me: https://github.com/sponsors/voxpelli
-
Released a new very simple 25 lines of code #npm module that validates #conventionalCommits messages in eg. a #husky "commit-msg" #gitHook: https://github.com/voxpelli/validate-conventional-commit
Great for use with eg #releasePlease to achieve #npmProvenance on #GitHubActions
-
Released a new very simple 25 lines of code #npm module that validates #conventionalCommits messages in eg. a #husky "commit-msg" #gitHook: https://github.com/voxpelli/validate-conventional-commit
Great for use with eg #releasePlease to achieve #npmProvenance on #GitHubActions
-
Released a new very simple 25 lines of code #npm module that validates #conventionalCommits messages in eg. a #husky "commit-msg" #gitHook: https://github.com/voxpelli/validate-conventional-commit
Great for use with eg #releasePlease to achieve #npmProvenance on #GitHubActions
-
Released a new very simple 25 lines of code #npm module that validates #conventionalCommits messages in eg. a #husky "commit-msg" #gitHook: https://github.com/voxpelli/validate-conventional-commit
Great for use with eg #releasePlease to achieve #npmProvenance on #GitHubActions
-
Released a new very simple 25 lines of code #npm module that validates #conventionalCommits messages in eg. a #husky "commit-msg" #gitHook: https://github.com/voxpelli/validate-conventional-commit
Great for use with eg #releasePlease to achieve #npmProvenance on #GitHubActions