Package dependencies error: ./node_modules/mdast-util-to-hast/lib/index.js Module not found: Can't resolve 'devlop'

[Jonathan-de-Villiers]

Package dependencies error: ./node_modules/mdast-util-to-hast/lib/index.js Module not found: Can't resolve 'devlop'

[remcohaszing]

This sounds like the latest of Expo doesn’t support support package exports. It’s a bug on their end.

[wooorm]

Are you using webpack 4, create react app?

[Jonathan-de-Villiers]

I'm not sure it is an old app that started development back in 2018

[wooorm]

You're using outdated and unmaintained tools. Switch to maintained and modern ones in order to use maintained and modern packages. Or use old versions of packages.

[github-actions]

Hi! This was closed. Team: If this was fixed, please add phase/solved. Otherwise, please add one of the no/* labels.

[bartvanandel]

This issue haunts us too. Expo-based app, using latest expo and pretty much all the latest package updates (bearing in mind expo compatibility). We're also on the latest LTS version of Node, and newest NPM, so "you're using outdated and unmaintained tools" definitely doesn't apply to us. The only thing we can't do is use "type": "module" in our package.json, because this breaks the build in weird ways which I wasn't able to fix in a few days worth of debugging.

The package is installed in node_modules correctly though. Checked npm list --all for anomalies, all good. Very strange.

[ChristianMurphy]

@bartvanandel sorry you ran into a spot of trouble.
The issue remains with Expo, which in return relies on metro.
Metro has known issues handling standard ESM and export specifiers https://github.com/search?q=repo%3Afacebook%2Fmetro+esm&type=issues
Metro and Expo need to resolve their issues.