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
As a result of last weeks working session, we are going to begin researching all of the various package.json fields and collecting it all into one place. I envision a "research hub" of sorts. At first, this will be a collection of markdown files in a GitHub repository (I'm working with @ljharb to get this started). Later, we could build some sort of public website for better access to the research.
This issue is meant to be a public record declaration of our continued efforts for standardizing package.json. As I explained in the previous package.json related thread, we are looking at a new, bottom-up approach. This approach will have multiple smaller efforts (starting with this one) with the collective end goal of standardizing and improving the developer experience of package.json.
The text was updated successfully, but these errors were encountered:
As a result of last weeks working session, we are going to begin researching all of the various package.json fields and collecting it all into one place. I envision a "research hub" of sorts. At first, this will be a collection of markdown files in a GitHub repository (I'm working with @ljharb to get this started). Later, we could build some sort of public website for better access to the research.
This issue is meant to be a public record declaration of our continued efforts for standardizing package.json. As I explained in the previous package.json related thread, we are looking at a new, bottom-up approach. This approach will have multiple smaller efforts (starting with this one) with the collective end goal of standardizing and improving the developer experience of package.json.
The text was updated successfully, but these errors were encountered: