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

Core: Wrap manager entries to handle exports using a cache directory #20331

Merged
merged 6 commits into from
Dec 23, 2022

Conversation

ndelangen
Copy link
Member

Issue: managerEntries can break when they contains exports

What I did

see: #20308

This would also allow us to provide cleaner locations without special characters in the paths for managerEntries.

@ndelangen ndelangen self-assigned this Dec 19, 2022
@ndelangen ndelangen requested review from tmeasday and shilman and removed request for tmeasday December 19, 2022 16:58
@ndelangen ndelangen changed the title apply same changes as before, but this time use the cacheDir Core: Wrap manager entries to handle exports using a cache directory Dec 19, 2022
Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Still not 100% confident, but let's see what users say

@ndelangen ndelangen changed the title Core: Wrap manager entries to handle exports using a cache directory Build: Wrap manager entries to handle exports using a cache directory Dec 23, 2022
@ndelangen ndelangen changed the title Build: Wrap manager entries to handle exports using a cache directory Core: Wrap manager entries to handle exports using a cache directory Dec 23, 2022
@ndelangen ndelangen merged commit 25f412c into next Dec 23, 2022
@ndelangen ndelangen deleted the fix/manager-entry-with-exports branch December 23, 2022 15:12
@VidunderGunder
Copy link

VidunderGunder commented Jan 6, 2023

I make this mistake all the time myself, but it's a bit risky to use types from before a breaking change.

{
  "@types/find-cache-dir": "^3.2.1",
  "find-cache-dir": "^4.0.0",
}

Maybe a test to check for mismatching types would be prudent?

Anyways, this may be a pointer:

v4.0.0

Breaking

Require Node.js 14 sindresorhus/find-cache-dir@c5e8e5c
This package is now pure ESM. Please read this.

Wishing you the best of luck, and I'm looking forward to have this solved to get back on the newest beta version 🙏

@ndelangen
Copy link
Member Author

Thanks for spotting that @VidunderGunder ❤️

I've opened a PR downgrading for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants