Verdaccio Roadmap #1690
Replies: 5 comments 4 replies
-
awesome! |
Beta Was this translation helpful? Give feedback.
-
Do we also need to look into fixing the CodeQL errors? Its seems to be complaining about valid issues like hardcoded header values etc. |
Beta Was this translation helpful? Give feedback.
-
No, that's something we are using in a experimental way. Ignore them for now please. |
Beta Was this translation helpful? Give feedback.
-
Any plans or aspiration to convert the codebase to ES Modules? |
Beta Was this translation helpful? Give feedback.
-
I'm all into ESM on the server side; won't use anything else now. One just needs to know the odd .cjs file extension trick. True that some testing frameworks are still catching up though. Plus if I can bundle up a Node.JS app into a single .js file, can't see why cannot do same in the browser. Like all things it took me baby steps to get there but after a few weeks playing around reckon I grok ESM very well now :D |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm @juanpicado and the intent of this story (epic) is to describe what we would like to have for Verdaccio next major.
https://github.com/verdaccio/verdaccio/tree/master
next major milestone
https://github.com/verdaccio/verdaccio/milestone/22
or
This year we will have a longer release, the project has grown and with a long tail of users, and at this point, we did not want to introduce big breaking changes in order to keep the backward compatibility.
Verdaccio next major release will keep the nature of the predecessors, simple, zero-configuration need it, lightweight and open-source but with a few breaking changes.
The project needs to evolve and might break some plugins or configurations, so in order to achieve a calm transition beta and alpha will be longer, as usual, better migration guides and so on, not to mention we are doing this on our spare time. We will define a final date release when we are sure we have enough topics closed. Verdaccio 5 still will be the major release and maintained as usual.
As a reminder, we accept donations, this helps keep motivation up and move things faster.
If you want to contribute, feel free to open a discussion about any of these topics, or something else you think would be relevant, do not hesitate to reach me out.
Structure
In the past was structured in several repositories, currently for the next major all the source code is hosted on this repository.
Source code cleanup
A clean code base is a signal of it health, there is a lot of pending task, lint, callback hell, replace dependencies by native code, etc:
Apply latest@verdaccio/babel-preset
and@verdaccio/eslint-config
,@verdaccio/types
.pnpm lint
and update--max-warnings 49
script.feat: use readable-stream 3 · Issue #32 · verdaccio/monorepo · GitHubasync/await
instead callbacks. Get rid of async dependency #1225Plugins
The Plugin support, the main pain comes from there, here a resume of the tickets we would like to address in the major release.
Endpoints
Fix Legacy
DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
messageUI
Project
documentation
open at website Issues · verdaccio/website · GitHubMigrate from 5.x to 6.x
During the maintenance of verdaccio@5.x some feature were included but not fully ported to the master branch, here the list of PR still pending to be moved which are labeled as
6.x pending
:This is a quite long list of tickets, most of them won't be achieve without your help. Verdaccio maintainers has as firs task guard for stability, help community, bug fixes, releases, promotion and as last in this list improvements.
Feel free to comment any of the tickets if you have further questions.
Beta Was this translation helpful? Give feedback.
All reactions