5.5 KiB
| author | authorURL | authorFBID | title |
|---|---|---|---|
| Juan Picado | https://twitter.com/jotadeveloper | 1122901551 | Release 4.3.0 |
Verdaccio keeps growing thanks to their users. This release is a minor one we do every month, further information about our releases can be read here.
Furthermore, the info about the release is also available at the GitHub releases page.
We have some highlights to share:
- At this stage, Docker 🐳 pulls have grown to 5.7 million pulls.
- We just reached 7.9k 🌟, would you help us to reach 10k? Give us your star ⭐️!
- Blog 🗒: Don't miss our new entry Managing multiple projects with Lerna and Yarn Workspaces by @sergiohgz.
- Monorepo: Along the last months we have crafted our monorepo for grouping all our ecosystem, plugin, core and tooling packages. This does not mean Verdaccio will become a monorepo, rather it will help us to grow without affecting the main repository and do easy updates or respond fast to mistakes in any release.
- Hacktoberfest 🎃 is here: We have prepared a guide if you want to contribute to Verdaccio, feel free to read it and give us feedback.
If you 😍 Verdaccio as we do, help us to grow more by donating to the project via OpenCollective.
Thanks for supporting Verdaccio ! 👏👏👏👏.
Use this version
Docker
docker pull verdaccio/verdaccio:4.3.0
npmjs
npm install -g verdaccio@4.3.0
Experiment Flags
This release includes a new property named experiments that can be placed in the config.yaml and is completely optional.
We want to be able to ship new things without affecting production environments. This flag allows us to add new features and get feedback from the community that wants to use them.
The features that are under this flag might not be stable or might be removed in future releases.
New Features
Browse web packages by version by @juanpicado
When you publish a new version of your package, you want to be able to access the previous ones, that's exactly what you can do with this new release.
Note the README always points to the latest release, Verdaccio does not persist the readme on each publish. This might change in the future, file a ticket if you are interested and might be considered if there is enough 👍🏻 votes.
npm token command support by @juanpicado, @Eomm and @juangabreil.
The command npm token is really useful to generate multiple tokens. This release ships some partial support for it and is flagged as experiment, to enable it you must do the following in your config file.
experiments:
token: true
You can find further technical information here.
Other updates
- (Docker) Node.js update to v10.16.3 #1473 by @juanpicado
- (Logging) Ensure every log file has at least one record #1414 by @mlucool
- UI: fix: correctly load font files - closes #134 by @DanielRuf
- UI: fix(ui): fix the hover effect on the packageItem's author area #137 by @FilipMessa
- UI: chore: pumped mui version #131 by @priscilawebdev
- UI: fix: sidebar view on small screens #136 by @juanpicado
- Monorepo: fix(security): Cross-site Scripting (XSS) for readme #145 by @juanpicado
- Monorepo: remove eslint warnings #112 by @sergiohgz
- Monorepo: chore: use Alpine image in DevContainers #100 by @sergiohgz
- Monorepo: ci: publish every commit in a temporal in-memory registry #74 by @sergiohgz
Verdaccio v3
Verdaccio 3 is still under our security maintenance state, thus we just shipped a minor update v3.13.1.
- Docker image updated to Node.js v10.16.3
- Update core dependencies
We update as much as possible without breaking the current implementation, thus storage or htpasswd are not part of this update.
Use this version
Docker
docker pull verdaccio/verdaccio:3.13.1
npmjs
npm install -g verdaccio@3.13.1
or
npm i -g verdaccio@previous