Module Resolution issues when building with Astro about react-portabletext

[tillschweneker]

Hey @rexxars,

I can confirm the issue and added a PR for @portabletext/react and @portabletext/toolkit.

[rshackleton]

@tillschweneker Surprisingly the build worked on Vercel when I pushed up a branch with these changes.

Nuking the node_modules and lock files and reinstalling worked. I think I'd done everything but delete the lock file previously. Thanks for the assist.

[rexxars]

This should be fixed as of v2.0.1 - please give it a try!

[JumboLove]

I took a look at publint and there might be something in the package build step that is incorrectly publishing files:

https://publint.bjornlu.com/@portabletext/[email protected]

[tillschweneker]

@JumboLove In the meantime you can fix the issue by adding this to your package.json. The original packages will be overridden by the ones from my GitHub.

"overrides": {
    "@portabletext/react": "tillschweneker/react-portabletext",
    "@portabletext/toolkit": "tillschweneker/toolkit"
}

[JumboLove]

Thank you @tillschweneker for the quick fix!

[rshackleton]

The overrides option isn't working for me, the @portabletext/toolkit package still throws the same resolution error.

Any change those PRs can be merged so the issue is fixed? The packages are completely unusable to an entire ecosystem currently.

[tillschweneker]

@rshackleton Did you try to delete your node_modules folder and package-lock.json and run npm i again?

[rshackleton]

I've nuked my node_modules and yarn.lock and updated to v2.0.1 of @portabletext/toolkit and the package.json is still missing the "type": "module" property which causes the issue.

Looks like the PR wasn't merged: portabletext/toolkit#6

[rshackleton]

Ah I was trying to get this working in a demo site but a dependency was forcing a lower version, ensuring all versions are on 2.0.1 has actually resolved the issue. Thanks!

[JumboLove]

Works great now! Thanks!

https://publint.dev/@portabletext/[email protected]