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

Document customizing by patch-package? #10

Closed
brodybits opened this issue Nov 1, 2017 · 3 comments
Closed

Document customizing by patch-package? #10

brodybits opened this issue Nov 1, 2017 · 3 comments

Comments

@brodybits
Copy link
Contributor

I recently discovered patch-package which makes it easy to customize without the need for forking.

I would be happy to contribute documentation assuming this project keeps a permissive license (#9), will need a few weeks due to existing commitments.

@rhyneav
Copy link
Member

rhyneav commented Nov 1, 2017

Patch-package looks interesting, but is it only for patching NPM modules? I'm all for adding it (and cool new things in general), but I just want to understand where this would be useful first.

And yes, this project will keep a permissive license. I'll work on making that more explicit.

@brodybits
Copy link
Contributor Author

Patch-package looks interesting, but is it only for patching NPM modules?

I think yes, at least so far (gotta admit I haven't tried it myself). My idea was just to document it as an option. Maybe not so relevant since I realized this project is more of a starter template. (It would be nice to see PaperCSS as a reusable HTML or web component, when we have convergence someday.)

And yes, this project will keep a permissive license. I'll work on making that more explicit.

Thanks for the response.

@rhyneav
Copy link
Member

rhyneav commented Dec 27, 2017

Hey @brodybits I'm going to go ahead and close this for now. Feel free to reopen if you want to go in and add details on Patch-package! I think it could be useful for those wanting to override some PaperCSS styles if they npm install papercss

@rhyneav rhyneav closed this as completed Dec 27, 2017
rhyneav pushed a commit that referenced this issue Oct 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants