![]() But npm is a package manager! It shouldn’t make you manage packages, that’s its job! There are a handful of places in npm where v6 and earlier versions sort of throw up their hands and make you fix stuff by yourself. We’ve gone through the entire project from the data management to the presentation layers, stripping output that doesn’t provide worthwhile information. Or, in other words “make npm yell at you less”. Npm v7 is based on a handful of technical and user experience principles, and each post in this series will tie back to one or more of these in some way. So, instead, this is the first post, with more to come, where I take you all through some of the major changes coming in npm v7, the thinking and motivation behind them, and how they might affect you and your work. This post started as a brief update on what we’ve been doing, intended to go live along with the talk, but it got long. The Q&A session was awesome, and it was clear that a lot of you are excited for this update to the npm CLI, and have a lot of questions that unfortunately couldn’t be adequately answered in such a short time. Yesterday, Edward Thomson presented a demo of a few of the features coming in npm v7 at GitHub Satellite. ![]() We’re overdue for a status update on npm v7.ĭespite some massive distracting changes (some unfortunate, some very fortunate), development work has been proceeding steadily. Quite a lot has happened in npm since our last update way back in 2019. Updates from the npm team are now published on the
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |