Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Problems building packages
See original GitHub issueI’ve had trouble using patch-package on a lot of projects.
Not all npm packages will publish all the files needed to build from scratch.
If a project only publishes an uglified dist folder to npm, is there a way to effectively use patch-package with it?
I’ve run into an issue where the src folder has been published to npm, but some config files have not been published so it’s not easy to do the build step. Do I just have to copy over the missing files from GitHub to do the build or am I missing something with how this package should be used?
This is a related issue that assumes you edit the src folder and then build again:
https://github.com/ds300/patch-package/issues/12
The issues I’ve run into here seem to happen with every package I try and edit, so I’m not sure if I’m misunderstanding how patch-package should be used, or it’s just extremely limited as to when it can be used.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hope you don’t mind if I close this issue. Glad to answer further questions, but this isn’t an actionable item so I’d prefer to tidy up. Thanks!
Sounds like you should create an issue there, asking to add the relevant files into the npm package.
What you are discribing here is inconvenient, but there nothing you can do from patch-package side if the package is missing some key files.