Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: documentation tried to access micromark, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound. #1381

Closed
waqas385 opened this issue May 19, 2021 · 3 comments
Assignees

Comments

@waqas385
Copy link

waqas385 commented May 19, 2021

What?

I upgraded documentation version from v13.2.1 to v13.2.5 and faces an issue while creating a jsDoc i.e
Error: documentation tried to access micromark, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound

Reproducing steps

  1. Upgrade documentation to v13.2.5
  2. Ran command to create jsDoc e.g yarn documentation build myapp-api/**/*.js -f html -o docs/generated/atea-api/
  3. Throw following error

Error: documentation tried to access micromark, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Required package: micromark (via "micromark/dist/character/markdown-line-ending")
Required by: documentation@npm:13.2.5 (via /xyzfolder/.yarn/cache/documentation-npm-13.2.5-2e2a7dce48-3f72cd5ae5.zip/node_modules/documentation/src/)

Investigation at my end

As per error message it seems that documentation has missing dependency package micromark and also unable to to find it within package.json of documentation package.

Suggestion: Add micromark as dependency within documentation package or do I need to add this dependency within my application?

version
v 13.2.5

Yarn version
2.x

@anthony-redFox anthony-redFox self-assigned this May 19, 2021
anthony-redFox added a commit to anthony-redFox/documentation that referenced this issue May 19, 2021
@waqas385
Copy link
Author

Thank you @anthony-redFox 👍

@JaimeObregon
Copy link

JaimeObregon commented Dec 21, 2021

I have stumbled upon this today and I can confirm it still happens. Using yarn 2. Has @anthony-redFox's fix been merged?

@anthony-redFox
Copy link
Member

Hello it have been merged but not released yet, we are working on major release so you can check on master branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants