Softverovich
Softverovich
I'm not so sure that this is definitely related to the building process of your project. What file are you getting this error from in your project? That error tells...
@ds300 are you still maintaining this project?
> Yarn 2/3 has built-in patching, you don't need this package: https://yarnpkg.com/cli/patch Sure - if you don't want the features of `patch-package` then go use the in-built `yarn patch`. This...
> @FilipMaslovaric It may be news to people who are unaware that Yarn supports this natively now. > > > > Furthermore, yarn patches and the patches produced by `patch-package`...
Any movement on this issue? It's been around for a while now (see #187)
@ariccio I think you're barking up the wrong tree :(. This issue may be open, but it seems like it's definitely stale and hasn't been caught by a bot. If...
Deleting `package-lock.json` and `Podfile.lock` should **ABSOLUTELY NOT** be the default or part of the `-auto` command. Both files exist specifically to lock down the versions of packages being used, and...
@mikehardy just FYI, using Bundler, the Ruby package manager, and something like `.ruby-version` to pin your version of Ruby through an environment manager tool for your local project has been...
Yep, 100% agree - the default position should be a bare-bones project, that's why I was thinking to myself "hmm, I just want it to be able to capture the...
This should be archived tbh - dead for years