Bug: `native` platform exports are pointing to the incorrect files when also building `node` about packemon HOT 5 CLOSED

I can confirm that using native platform without subpaths works fine.

from packemon.

@j3tan So I can't reproduce this: #189

The fs output I see locally is exactly what I expect it to be and does not look like yours. I did notice an issue with type paths but that wouldn't cause what you're seeing.

from packemon.

I think the issue is that there is no fallback "types" field exported, so if a package is being built for npm publishing, the types
for an import to the /types path will not be found. Once that "default"/fallback "types" field was added in I was able to build successfully
I created a PR with a fix: #194

from packemon.

So the previous issue I created the PR for seems to actually be a separate issue, but for the specific issue @j3tan is describing, I think this would be the/a fix: #195

from packemon.

fixed in #194

from packemon.