Skip to content

Conversation

@tonycoco
Copy link
Contributor

Fixes problems with #856 by updating rimraf to v5.0.5 and adjusting the code to reflect API changes

@tonycoco
Copy link
Contributor Author

Odd error happening with this update with the license checker. Looking into it...

@tonycoco tonycoco force-pushed the rimraf_updates branch 2 times, most recently from 72ea670 to b051ff1 Compare March 26, 2024 21:41
@tonycoco
Copy link
Contributor Author

It seems that the newer version of rimraf has unpublished repos used in it. I tried to allowlist the ones it complains about but have not found a solution yet. FYI: https://github.com/isaacs/rimraf

@danielbankhead
Copy link
Contributor

In Node.js 18 we may not need rimraf. See the recursive option here:

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

Successfully merging this pull request may close these issues.

2 participants