FYI: you link to the NPM package several places in the article, but the package.json is apparently missing a link to the associated git repo.
I can't speak for everyone obviously, but I have no interest in npmjs.org links. I only use them to find the associated git repo. For anyone else looking for the git repo, you can find it here: github.com/cloudnc/observable-webw... (the last link in the article references it).
(also, thanks for open-sourcing your work! Looks super useful)
I'm a full stack Typescript developer specialising in Angular and Node. I love reactive programming with RxJS, utilising the less-used web APIs and I'm passionate about polymorphic full stack TS.
Thanks for the tip John, I have actually already fixed this however it hasn't been released due to the semantic release program computing the change was immaterial and didn't warrant a version bump, so this fix will go out with the next addition to the library. I'll see if there is anything obvious I can fix up to ensure it gets out as this is kinda annoying I agree.
Dunno what your pipeline is, but I remember running into something like this with lerna and I was able to make use of an option (--force ? --force-publish ?) to force out an otherwise identical patch release.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
FYI: you link to the NPM package several places in the article, but the
package.jsonis apparently missing a link to the associated git repo.I can't speak for everyone obviously, but I have no interest in npmjs.org links. I only use them to find the associated git repo. For anyone else looking for the git repo, you can find it here: github.com/cloudnc/observable-webw... (the last link in the article references it).
(also, thanks for open-sourcing your work! Looks super useful)
Thanks for the tip John, I have actually already fixed this however it hasn't been released due to the semantic release program computing the change was immaterial and didn't warrant a version bump, so this fix will go out with the next addition to the library. I'll see if there is anything obvious I can fix up to ensure it gets out as this is kinda annoying I agree.
Dunno what your pipeline is, but I remember running into something like this with lerna and I was able to make use of an option (
--force?--force-publish?) to force out an otherwise identical patch release.