1
0
mirror of https://github.com/verdaccio/verdaccio.git synced 2024-11-13 03:35:52 +01:00
verdaccio/website/blog/2019-07-08-verdaccio-410-release.md
Sergio Moreno a6b0d63afb
feat: migrate Verdaccio.org to Docusaurus v2 and new design (#2343)
Co-authored-by: Juan Picado <juanpicado19@gmail.com>
2021-07-27 21:52:49 +02:00

3.6 KiB
Raw Permalink Blame History

author authorURL authorFBID title
Juan Picado https://twitter.com/jotadeveloper 1122901551 Release 4.1.0

Verdaccio keeps growing thanks to their users. This release is a minor one we do every month, for further information about our releases can be read here.

Furthermore, the info about the release is also available at GitHub releases page.

We have some highlights to share:

If you 😍 Verdaccio as we do, helps us to grow more donating to the project via OpenCollective.

Thanks for support Verdaccio ! 👏👏👏👏.

Use this version

Docker

docker pull verdaccio/verdaccio:4.1.0

npmjs

npm install -g verdaccio@4.1.0

New Features

Filter plugin for packages by @mlucool

Verdaccio now support plugin filters, we are just starting with filter metadata.

It gets a current copy of a package metadata and may choose to modify it as required. For example, this may be used to block a bad version of a package or add a time delay from when new packages can be used from your registry. Errors in a filter will cause a 404, similar to upLinkErrors as it is not safe to recover gracefully from them.

The configuration would looks like

filters:
  storage-filter-blackwhitelist:
    filter_file: /path/to/file

The current API for the plugin is

interface IPluginStorageFilter<T> extends IPlugin<T> {
  filter_metadata(packageInfo: Package): Promise<Package>;
}

This system might be extended in the future, we are trying this approach at this stage.

parse YAML/JSON/JS config file by @honzahommer

Now, Verdaccio is able to understand JSON format for configuration files.

verdaccio --config /myPath/verdaccio.json

New CLI command verdaccio --info by @jamesgeorge007

The new verdaccio --info command will display information of your environment, this sort of information is handy in order to report any bug.

$ verdaccio --info

Environment Info:

  System:
    OS: macOS 10.14
    CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
  Binaries:
    Node: 10.15.0 - ~/.nvm/versions/node/v10.15.0/bin/node
    Yarn: 1.16.0 - ~/.nvm/versions/node/v10.15.0/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.15.0/bin/npm
  Virtualization:
    Docker: 19.03.0 - /usr/local/bin/docker
  Browsers:
    Chrome: 75.0.3770.100
    Firefox: 67.0.3
    Safari: 12.0
  npmGlobalPackages:
    verdaccio: 4.0.0