-
It looks like you've bumped the version number to 1.2.0, but have not published to npm.
If you want to update the version that is delivered via `npm install`, you need to run `npm publish`.
(If you'…
-
Can you please publish this package on npm too?
-
It looks like the latest version on NPM doesn't match the latest version on github releases. Could you do an `npm publish`? Would be very useful for the new main entry point (webpack support).
-
please.
-
I am trying to set up my lerna monorepo in the following way:
there is an external and an internal client in `~/packages/client`. `internal` is supposed to be released to the Github Package Registr…
-
Hey Jeff,
Any plans to publish this to NPM proper?
The GitHub registry isn't very ergonomic to install packages from. It requires a GitHub token, even when the packages are public.
-
To allow using the core validator in bespoke pipelines, I would love to see it published as a standalone package on npm.
-
Any reason the fetchPolicy: 'no-cache' edit in gatsby-source-prismic-graphql/packages/gatsby-source-prismic-graphql/src/components/WrapPage.tsx
Has not been published to NPM yet?
That would fix my…
-
That would nice. I actually published this to NPM under `scotch-panels` and a fork of mine.
If you want to take over the name under your org on npm, just let me know and I'll transfer.
-
PR:
- https://github.com/openscd/open-scd/pull/1485
trusz updated
2 months ago