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
Explain your idea briefly
The CLI currently clones the package.json file from matterhorn. This copies over information regarding git, authorship, etc. In coordination with #3, the Git urls should be mapped over to the users new git repo (if remote is initialized). The authorship should be transferred to their name. Additionally, there needs to be some research done on how the lock-file works and if it is needed. Furthermore, should Matterhorn dependency versions be locked or can we continue to support latest using the ^ symbol. This issue in general is fairly open-ended and could be broken down into smaller contributions/issues if necessary.
What value will this add to the project?
Better user experience with NPM - the crux of many JS applications
Will you be contributing this yourself?
Will do further research and create standalone contributing items
What is this idea based on? List examples
Haven't seen this implemented but I think it could have great upstream impact if developed correctly
The text was updated successfully, but these errors were encountered:
Explain your idea briefly
The CLI currently clones the package.json file from matterhorn. This copies over information regarding git, authorship, etc. In coordination with #3, the Git urls should be mapped over to the users new git repo (if remote is initialized). The authorship should be transferred to their name. Additionally, there needs to be some research done on how the lock-file works and if it is needed. Furthermore, should Matterhorn dependency versions be locked or can we continue to support latest using the
^
symbol. This issue in general is fairly open-ended and could be broken down into smaller contributions/issues if necessary.What value will this add to the project?
Better user experience with NPM - the crux of many JS applications
Will you be contributing this yourself?
Will do further research and create standalone contributing items
What is this idea based on? List examples
Haven't seen this implemented but I think it could have great upstream impact if developed correctly
The text was updated successfully, but these errors were encountered: