|
|
|
|
|
by yemsalat
3536 days ago
|
|
Just to expand on the stricter versioning rules that I mentioned, some things that in my opinion could improve the reliability of a package repository: - strictly defined version update time intervals, e.g. you can't update your package more than once a week (or have to take some special actions for critical updates, e.g. contact support) - "delayed" publishing, e.g. when you submit your package it will only be published in 24 hours, until then you can re-submit updates, etc. - similar to above, but your package wont be published until it was tagged on github (or elsewhere) for a certain amount of time - published packages can not be removed, but you can disassociate them with your account by marking them as "not maintained" and possibly assign new maintainers for it - maybe introduce some way for developers to mark new versions as "backwards incompatible" if they do break backwards compatibility I think there is definitely a "market" for some stricter node package repo. |
|