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

remarkjs / react-markdown

Markdown component for React

https://remarkjs.github.io/react-markdown/

MIT License

13.27k stars 876 forks source link

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

Closed Jonathan-de-Villiers closed 1 year ago

Jonathan-de-Villiers commented 1 year ago

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

"react-markdown": "^9.0.1",

Link to runnable example

No response

Steps to reproduce

I've just installed the package using yarn. imported it to a file and tried to use it.

Expected behavior

Hoped it would work

Actual behavior

it gave me the error and even when I added devlop it still isn't working

Runtime

Node v16

Package manager

yarn 1

OS

Windows

Build and bundle tools

No response

wooorm commented 1 year ago

Are you using webpack 4, create react app?

Jonathan-de-Villiers commented 1 year ago

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

wooorm commented 1 year ago

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[bot] commented 1 year ago

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

bartvanandel commented 11 months ago

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.

remcohaszing commented 11 months ago

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

ChristianMurphy commented 11 months ago

@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.