Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework npm integration #8

Open
Ethan-Arrowood opened this issue Jan 28, 2019 · 0 comments
Open

Rework npm integration #8

Ethan-Arrowood opened this issue Jan 28, 2019 · 0 comments
Labels
Feature 🌟 New feature or request

Comments

@Ethan-Arrowood
Copy link
Contributor

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

@Ethan-Arrowood Ethan-Arrowood added the Feature 🌟 New feature or request label Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature 🌟 New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant