Wrong hash in Vite types file when installing in a pnpm monorepo

[lucastraba]

Describe the bug

I've been trying to use this plugin in a Vite package of my pnpm monorepo, but I can't, because in the Vite plugin, the import of the types file is: import 'unimport/dist/types-XXXXXX' And the actual file is: types-YYYYYY.d.ts

This seems to only happen with a pnpm monorepo setup, not when installing with npm (path and name match there).

Reproduction steps:

• Open the CodeSandbox below
• Go to test.js
• ctrl/cmd + click on the import path
• Check the hash of the types import
• Go to dist
• Check out types import filename

Actual: Import path hash has the same hash as the file

Expected: Import path matches file name

Reproduction

https://codesandbox.io/p/sandbox/zealous-sky-hq87mv?file=%2Ftest.js%3A1%2C46

System Info

Any. This is a build problem.

Used Package Manager

pnpm

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guide.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• [X] The provided reproduction is a minimal reproducible of the bug.

[lucastraba]

An update to this:

This is happening because of pnpm's hoisting. It seems that the unimport build happens separately and generates one hash and then unplugin-auto-import builds based on a different build or a different environment, and produces the wrong import.

Things I tried:

• Patching the correct hash: obviously doesn't work because it breaks if it ever gets regenerated
• Patching both dependencies: this is hacky and doesn't work in the CI pipeline
• Preventing hoisting of unimport: I couldn't get pnpm to not hoist it, no matter what I tried

I tried to see if I could come up with a fix and make a PR, but unfortunately I don't have the time to look into it with the amount of attention it would need. For anyone trying to fix it, it's specifically that: the the build of unimport combined with the build of unplugin-auto-import happening in a disconnected way due to pnpm's hoisting.

As it is, I have no choice but to remove the package from our project, but I'll keep an eye on this issue, because I'd really, really like to use this.

[lucastraba]

Bump :(

[toimc]

same here!

[lucastraba]

Any news about this? I'd really really like to use this plugin!

[lucastraba]

Bump?