Détail du package

@verdaccio/utils

verdaccio1.4mMIT6.0.0-6-next.44

verdaccio utilities

private, package, repository, registry

readme

BannerHelp

Verdaccio stands for peace, stop the war, we will be yellow / blue 🇺🇦 until that happens.

verdaccio logo

verdaccio gif

Version Next (Development Branch)

Looking for Verdaccio version 5 or 6? Version 6 is the latest version and successor to version 5. Version 6 requires Node.js 18 or higher and is maintained in the 6.x branch.

The plugins for versions 5 and 6 are located at the verdaccio/monorepo repository. Plugins for the next-8 version are hosted in this project under the ./packages/plugins folder.

Note that contributing guidelines might be different based on the branch.

Verdaccio is a simple, zero-config-required local private npm registry. No need for an entire database just to get started! Verdaccio comes out of the box with its own tiny database, and the ability to proxy other registries (eg. npmjs.org), caching the downloaded modules along the way. For those looking to extend their storage capabilities, Verdaccio supports various community-made plugins to hook into services such as Amazon's s3, Google Cloud Storage or create your own plugin.

Verdaccio Home MIT License Verdaccio Latest

Documentation Discord Bluesky Backers Sponsors

Verdaccio Downloads Docker Pulls GitHub Stars

StandWithUkraine

Versions

You can find more details about the different versions of Verdaccio, minimum requirements, as well as links to associated npm packages and docker images in the version history.

Install

Node.js v18 as minimum version required

Install with npm:

npm install -g verdaccio@next-8

With yarn

yarn global add verdaccio@next-8

With pnpm

pnpm i -g verdaccio@next-8

or

docker pull verdaccio/verdaccio:nightly-master

or with helm official chart.

helm repo add verdaccio https://charts.verdaccio.org
helm repo update
helm install verdaccio/verdaccio

Furthermore, you can read the Debugging Guidelines and the Docker Examples for more advanced development.

Plugins

You can develop your own plugins with the verdaccio generator. Installing Yeoman is required.

npm install -g yo
npm install -g generator-verdaccio-plugin

Learn more here how to develop plugins. Share your plugins with the community.

End to End Testing

In our compatibility testing project, we're dedicated to ensuring that your favorite commands work seamlessly across different versions of npm, pnpm, and Yarn. From publishing packages to managing dependencies. Our goal is to give you the confidence to use your preferred package manager without any issues. So dive in, check out our matrix, and see how your commands fare across the board!

Learn or contribute here

Commands

cmd npm6 npm7 npm8 npm9 npm10 pnpm8 pnpm9 pnpm10 yarn1 yarn2 yarn3 yarn4
publish
unpublish
info
audit
install
deprecate
ping
search
star
stars
dist-tag

notes:

  • yarn search cmd exist in modern but, it do not uses the search registry endpoint.
  • yarn modern has two info commands, the one used here is yarn npm info

❌ = no tested ✅ = tested ⛔ = no supported

Donations

Verdaccio is run by volunteers; nobody is working full-time on it. If you find this project to be useful and would like to support its development, consider doing a long support donation - and your logo will be on this section of the readme.

Donate 💵👍🏻 starting from $1/month or just one single contribution.

What does Verdaccio do for me?

Use private packages

If you want to use all benefits of npm package system in your company without sending all code to the public, and use your private packages just as easy as public ones.

Cache npmjs.org registry

If you have more than one server you want to install packages on, you might want to use this to decrease latency (presumably "slow" npmjs.org will be connected to only once per package/version) and provide limited failover (if npmjs.org is down, we might still find something useful in the cache) or avoid issues like _How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript, Many packages suddenly disappeared or Registry returns 404 for a package I have installed before_.

Link multiple registries

If you use multiples registries in your organization and need to fetch packages from multiple sources in one single project you might take advance of the uplinks feature with Verdaccio, chaining multiple registries and fetching from one single endpoint.

Override public packages

If you want to use a modified version of some 3rd-party package (for example, you found a bug, but maintainer didn't accept pull request yet), you can publish your version locally under the same name. See in detail here.

E2E Testing

Verdaccio has proved to be a lightweight registry that can be booted in a couple of seconds, fast enough for any CI. Many open source projects use Verdaccio for end to end testing, to mention some examples, create-react-app, mozilla neutrino, pnpm, storybook, babel.js, angular-cli or docusaurus. You can read more in here.

Furthermore, here few examples how to start:

Watch our Videos

Node 2022, February 2022, Online Free

You might want to check out as well our previous talks:

Get Started

Run in your terminal

verdaccio

You would need set some npm configuration, this is optional.

npm set registry http://localhost:4873/

For one-off commands or to avoid setting the registry globally:

NPM_CONFIG_REGISTRY=http://localhost:4873 npm i

Now you can navigate to http://localhost:4873/ where your local packages will be listed and can be searched.

Warning: Verdaccio does not currently support PM2's cluster mode, running it with cluster mode may cause unknown behavior.

Publishing

1. create a user and log in

npm adduser --registry http://localhost:4873

if you use HTTPS, add an appropriate CA information ("null" means get CA list from OS)

npm set ca null

2. publish your package

npm publish --registry http://localhost:4873

This will prompt you for user credentials which will be saved on the verdaccio server.

Docker

Below are the most commonly needed information, every aspect of Docker and verdaccio is documented separately

docker pull verdaccio/verdaccio:nightly-master

Available as tags.

Running Verdaccio using Docker

To run the docker container:

docker run -it --rm --name verdaccio -p 4873:4873 verdaccio/verdaccio

Docker examples are available in this repository.

Compatibility

Verdaccio aims to support all features of a standard npm client that make sense to support in a private repository. Unfortunately, it isn't always possible.

Basic features

  • Installing packages (npm install, npm update, etc.) - supported
  • Publishing packages (npm publish) - supported

Advanced package control

  • Unpublishing packages (npm unpublish) - supported
  • Tagging (npm dist-tag) - supported
  • Deprecation (npm deprecate) - supported

User management

  • Registering new users (npm adduser {newuser}) - supported
  • Change password (npm profile set password) - supported
  • Transferring ownership (npm owner) - supported
  • Token (npm token) - supported

Miscellaneous

  • Searching (npm search) - supported (cli / browser)
  • Ping (npm ping) - supported
  • Starring (npm star, npm unstar, npm stars) - supported

Security

  • Audit (npm/yarn audit) - supported

Report a vulnerability

If you want to report a security vulnerability, please follow the steps which we have defined for you in our security policy.

Special Thanks

Thanks to the following companies to help us to achieve our goals providing free open source licenses. Every company provides enough resources to move this project forward.

Company Logo License
JetBrains jetbrain JetBrains provides licenses for products for active maintainers, renewable yearly
Crowdin crowdin Crowdin provides platform for translations
BrowserStack browserstack BrowserStack provides plan to run End to End testing for the UI
Netlify netlify Netlify provides pro plan for website deployment
Algolia algolia Algolia provides search services for the website
Docker docker Docker offers unlimited pulls and unlimited egress to any and all users

Maintainers

Juan Picado Ayush Sharma Sergio Hg
jotadeveloper ayusharma sergiohgz
@ayusharma_ @sergiohgz
Priscila Oliveria Daniel Ruf
priscilawebdev DanielRuf
@priscilawebdev @DanielRufde

You can find and chat with them over Discord, click here.

Who is using Verdaccio?

🤓 Don't be shy, add yourself to this readme.

Open Collective Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

sponsor sponsor sponsor sponsor sponsor sponsor sponsor sponsor sponsor sponsor

Open Collective Backers

Thank you to all our backers! 🙏 [Become a backer]

backers

Contributors

This project exists thanks to all the people who contribute. [Contribute].

contributors

FAQ / Contact / Troubleshoot

If you have any issue you can try the following options. Do no hesitate to ask or check our issues database. Perhaps someone has asked already what you are looking for.

License

Verdaccio is MIT licensed

The Verdaccio documentation and logos (excluding /thanks, e.g., .md, .png, .sketch files within the /assets folder) are Creative Commons licensed.

changelog

@verdaccio/utils

6.0.0-6-next.44

Patch Changes

  • @verdaccio/core@6.0.0-6-next.76

6.0.0-6-next.43

Patch Changes

  • Updated dependencies [0a6412ca9]
    • @verdaccio/core@6.0.0-6-next.75

6.0.0-6-next.42

Patch Changes

  • @verdaccio/core@6.0.0-6-next.74

6.0.0-6-next.41

Patch Changes

  • Updated dependencies [f859d2b1a]
    • @verdaccio/core@6.0.0-6-next.73

6.0.0-6-next.40

Patch Changes

  • @verdaccio/core@6.0.0-6-next.72

6.0.0-6-next.39

Patch Changes

  • @verdaccio/core@6.0.0-6-next.71

6.0.0-6-next.38

Patch Changes

  • @verdaccio/core@6.0.0-6-next.70

6.0.0-6-next.37

Patch Changes

  • Updated dependencies [c9d1af0e]
    • @verdaccio/core@6.0.0-6-next.69

6.0.0-6-next.36

Patch Changes

  • @verdaccio/core@6.0.0-6-next.68

6.0.0-6-next.35

Patch Changes

  • Updated dependencies [16e38df8]
    • @verdaccio/core@6.0.0-6-next.67

6.0.0-6-next.34

Patch Changes

  • @verdaccio/core@6.0.0-6-next.66

6.0.0-6-next.33

Patch Changes

  • Updated dependencies [a1da1130]
    • @verdaccio/core@6.0.0-6-next.65

6.0.0-6-next.32

Patch Changes

  • Updated dependencies [974cd8c1]
    • @verdaccio/core@6.0.0-6-next.64

6.0.0-6-next.31

Patch Changes

  • Updated dependencies [dc571aab]
    • @verdaccio/core@6.0.0-6-next.63

6.0.0-6-next.30

Patch Changes

  • Updated dependencies [378e907d]
    • @verdaccio/core@6.0.0-6-next.62

6.0.0-6-next.29

Patch Changes

  • @verdaccio/core@6.0.0-6-next.61

6.0.0-6-next.28

Patch Changes

  • @verdaccio/core@6.0.0-6-next.60

6.0.0-6-next.27

Patch Changes

  • @verdaccio/core@6.0.0-6-next.59

6.0.0-6-next.26

Patch Changes

  • @verdaccio/core@6.0.0-6-next.58

6.0.0-6-next.25

Patch Changes

  • @verdaccio/core@6.0.0-6-next.57

6.0.0-6-next.24

Minor Changes

  • a1986e09: feat: expose middleware utils

Patch Changes

  • @verdaccio/core@6.0.0-6-next.56

6.0.0-6-next.23

Patch Changes

  • 9718e033: fix: build targets for 5x modules
  • Updated dependencies [9718e033]
    • @verdaccio/core@6.0.0-6-next.55

6.0.0-6-next.22

Minor Changes

  • ef88da3b: feat: improve support for fs promises older nodejs

Patch Changes

  • Updated dependencies [ef88da3b]
    • @verdaccio/core@6.0.0-6-next.54

6.0.0-6-next.21

Patch Changes

  • @verdaccio/core@6.0.0-6-next.53

6.0.0-6-next.20

Patch Changes

  • @verdaccio/core@6.0.0-6-next.52

6.0.0-6-next.19

Patch Changes

  • Updated dependencies [4b29d715]
    • @verdaccio/core@6.0.0-6-next.51

6.0.0-6-next.18

Patch Changes

  • @verdaccio/core@6.0.0-6-next.50

6.0.0-6-next.17

Patch Changes

  • @verdaccio/core@6.0.0-6-next.49

6.0.0-6-next.16

Minor Changes

  • 62c24b63: feat: add passwordValidationRegex property

Patch Changes

  • Updated dependencies [43f32687]
  • Updated dependencies [62c24b63]
    • @verdaccio/core@6.0.0-6-next.48

6.0.0-6-next.15

Patch Changes

  • @verdaccio/core@6.0.0-6-next.47

6.0.0-6-next.14

Patch Changes

  • Updated dependencies [b849128d]
    • @verdaccio/core@6.0.0-6-next.8

6.0.0-6-next.13

Patch Changes

  • Updated dependencies [351aeeaa]
    • @verdaccio/core@6.0.0-6-next.7

6.0.0-6-next.12

Major Changes

  • 292c0a37: feat!: replace deprecated request dependency by got

    This is a big refactoring of the core, fetching dependencies, improve code, more tests and better stability. This is essential for the next release, will take some time but would allow modularize more the core.

    Notes

    • Remove deprecated request by other got, retry improved, custom Agent ( got does not include it built-in)
    • Remove async dependency from storage (used by core) it was linked with proxy somehow safe to remove now
    • Refactor with promises instead callback wherever is possible
    • ~Document the API~
    • Improve testing, integration tests
    • Bugfix
    • Clean up old validations
    • Improve performance

    💥 Breaking changes

    • Plugin API methods were callbacks based are returning promises, this will break current storage plugins, check documentation for upgrade.
    • Write Tarball, Read Tarball methods parameters change, a new set of options like AbortController signals are being provided to the addAbortSignal can be internally used with Streams when a request is aborted. eg: addAbortSignal(signal, fs.createReadStream(pathName));
    • @verdaccio/streams stream abort support is legacy is being deprecated removed
    • Remove AWS and Google Cloud packages for future refactoring #2574.

Patch Changes

  • Updated dependencies [292c0a37]
  • Updated dependencies [a3a209b5]
  • Updated dependencies [00d1d2a1]
    • @verdaccio/core@6.0.0-6-next.6

6.0.0-6-next.11

Patch Changes

  • Updated dependencies [82cb0f2b]
  • Updated dependencies [5167bb52]
    • @verdaccio/core@6.0.0-6-next.5

6.0.0-6-next.10

Major Changes

  • a828271d: refactor: download manifest endpoint and integrate fastify

    Much simpler API for fetching a package

     const manifest = await storage.getPackageNext({
          name,
          uplinksLook: true,
          req,
          version: queryVersion,
          requestOptions,
     });

    not perfect, the req still is being passed to the proxy (this has to be refactored at proxy package) and then removed from here, in proxy we pass the request instance to the request library.

    Details

    • async/await sugar for getPackage()
    • Improve and reuse code between current implementation and new fastify endpoint (add scaffolding for request manifest)
    • Improve performance
    • Add new tests

    Breaking changes

    All storage plugins will stop to work since the storage uses getPackageNext method which is Promise based, I won't replace this now because will force me to update all plugins, I'll follow up in another PR. Currently will throw http 500

Minor Changes

  • 24b9be02: refactor: improve docker image build with strict dependencies and prod build
  • b13a3fef: refactor: improve versions and dist-tag filters

Patch Changes

  • Updated dependencies [24b9be02]
    • @verdaccio/core@6.0.0-6-next.4

6.0.0-6-next.9

Minor Changes

  • f86c31ed: feat: migrate web sidebar endpoint to fastify

    reuse utils methods between packages

6.0.0-6-next.8

Patch Changes

  • Updated dependencies [6c1eb021]
    • @verdaccio/core@6.0.0-6-next.3

6.0.0-6-next.7

Major Changes

  • 794af76c: Remove Node 12 support

    • We need move to the new undici and does not support Node.js 12

Minor Changes

  • 154b2ecd: refactor: remove @verdaccio/commons-api in favor @verdaccio/core and remove duplications

Patch Changes

  • Updated dependencies [794af76c]
  • Updated dependencies [154b2ecd]
    • @verdaccio/core@6.0.0-6-next.2

6.0.0-6-next.6

Major Changes

  • 459b6fa7: refactor: search v1 endpoint and local-database

    • refactor search api v1 endpoint, improve performance
    • remove usage of async dependency https://github.com/verdaccio/verdaccio/issues/1225
    • refactor method storage class
    • create new module core to reduce the ammount of modules with utilities
    • use undici instead node-fetch
    • use fastify instead express for functional test

    Breaking changes

    • plugin storage API changes
    • remove old search endpoint (return 404)
    • filter local private packages at plugin level

    The storage api changes for methods get, add, remove as promise base. The search methods also changes and recieves a query object that contains all query params from the client.

    export interface IPluginStorage<T> extends IPlugin {
      add(name: string): Promise<void>;
      remove(name: string): Promise<void>;
      get(): Promise<any>;
      init(): Promise<void>;
      getSecret(): Promise<string>;
      setSecret(secret: string): Promise<any>;
      getPackageStorage(packageInfo: string): IPackageStorage;
      search(query: searchUtils.SearchQuery): Promise<searchUtils.SearchItem[]>;
      saveToken(token: Token): Promise<any>;
      deleteToken(user: string, tokenKey: string): Promise<any>;
      readTokens(filter: TokenFilter): Promise<Token[]>;
    }

Patch Changes

  • Updated dependencies [459b6fa7]
    • @verdaccio/commons-api@11.0.0-6-next.4

6.0.0-6-next.5

Patch Changes

  • d2c65da9: Fixed the validation of the name when searching for a tarball that have scoped package name

6.0.0-6-next.4

Patch Changes

5.0.0-alpha.3

Patch Changes

  • fecbb9be: chore: add release step to private regisry on merge changeset pr
  • Updated dependencies [fecbb9be]
    • @verdaccio/commons-api@10.0.0-alpha.3

5.0.0-alpha.2

Minor Changes

  • 54c58d1e: feat: add server rate limit protection to all request

    To modify custom values, use the server settings property.

    server:
    
    ## https://www.npmjs.com/package/express-rate-limit#configuration-options
    
    rateLimit:
    windowMs: 1000
    max: 10000

    The values are intended to be high, if you want to improve security of your server consider using different values.

Patch Changes

  • Updated dependencies [54c58d1e]
    • @verdaccio/commons-api@10.0.0-alpha.2

5.0.0-alpha.1

Major Changes

  • d87fa026: feat!: experiments config renamed to flags

    • The experiments configuration is renamed to flags. The functionality is exactly the same.
    flags: token: false;
    search: false;
    • The self_path property from the config file is being removed in favor of config_file full path.
    • Refactor config module, better types and utilities
  • da1ee9c8: - Replace signature handler for legacy tokens by removing deprecated crypto.createDecipher by createCipheriv

    • Introduce environment variables for legacy tokens

    Code Improvements

    • Add debug library for improve developer experience

    Breaking change

    • The new signature invalidates all previous tokens generated by Verdaccio 4 or previous versions.
    • The secret key must have 32 characters long.

    New environment variables

    • VERDACCIO_LEGACY_ALGORITHM: Allows to define the specific algorithm for the token signature which by default is aes-256-ctr
    • VERDACCIO_LEGACY_ENCRYPTION_KEY: By default, the token stores in the database, but using this variable allows to get it from memory

Minor Changes

Patch Changes

  • b57b4338: Enable prerelease mode with changesets
  • 31af0164: ESLint Warnings Fixed

    Related to issue #1461

    • max-len: most of the sensible max-len errors are fixed
    • no-unused-vars: most of these types of errors are fixed by deleting not needed declarations
    • @typescript-eslint/no-unused-vars: same as above
  • Updated dependencies [d87fa026]

  • Updated dependencies [da1ee9c8]
  • Updated dependencies [26b494cb]
  • Updated dependencies [b57b4338]
  • Updated dependencies [31af0164]
    • @verdaccio/commons-api@10.0.0-alpha.1

5.0.0-alpha.1

Major Changes

  • d87fa0268: feat!: experiments config renamed to flags

    • The experiments configuration is renamed to flags. The functionality is exactly the same.
    flags: token: false;
    search: false;
    • The self_path property from the config file is being removed in favor of config_file full path.
    • Refactor config module, better types and utilities
  • da1ee9c82: - Replace signature handler for legacy tokens by removing deprecated crypto.createDecipher by createCipheriv

    • Introduce environment variables for legacy tokens

    Code Improvements

    • Add debug library for improve developer experience

    Breaking change

    • The new signature invalidates all previous tokens generated by Verdaccio 4 or previous versions.
    • The secret key must have 32 characters long.

    New environment variables

    • VERDACCIO_LEGACY_ALGORITHM: Allows to define the specific algorithm for the token signature which by default is aes-256-ctr
    • VERDACCIO_LEGACY_ENCRYPTION_KEY: By default, the token stores in the database, but using this variable allows to get it from memory

Minor Changes

Patch Changes

  • b57b43388: Enable prerelease mode with changesets
  • 31af01641: ESLint Warnings Fixed

    Related to issue #1461

    • max-len: most of the sensible max-len errors are fixed
    • no-unused-vars: most of these types of errors are fixed by deleting not needed declarations
    • @typescript-eslint/no-unused-vars: same as above
  • Updated dependencies [d87fa0268]

  • Updated dependencies [da1ee9c82]
  • Updated dependencies [26b494cbd]
  • Updated dependencies [b57b43388]
  • Updated dependencies [31af01641]
    • @verdaccio/commons-api@10.0.0-alpha.0