You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We seem to use this as a default in many projects.
For example, a PHP project, a WordPress project, a JS project, a Vue project - etc etc. But - then when we update it.... really / there's nothing that connects it back.
Should it be officially and forever - just something you download? Or should it be something that's versioned and updated?
How would that work?
Sounds like a good example to think about @alpha-four, five and six!
The text was updated successfully, but these errors were encountered:
itd be cool if it was like a package we could download with npm/yarn.
im not sure about versioning beyond perpetually updating it. which ofcourse. but i dont see why youd want to go to previous versions. i think any new version should always do wtv older versions did + more
We seem to use this as a default in many projects.
For example, a PHP project, a WordPress project, a JS project, a Vue project - etc etc. But - then when we update it.... really / there's nothing that connects it back.
Should it be officially and forever - just something you download? Or should it be something that's versioned and updated?
How would that work?
Sounds like a good example to think about @alpha-four, five and six!
The text was updated successfully, but these errors were encountered: