Module not found: Can't resolve 'yaml'

Open
#2,754 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
next.js, typescript
Domain
frontend

Research direction

Start with the RedocComponent entry point and its RedocStandalone import in the reported Next project. Reproduce the “Can't resolve 'yaml'” build error, then trace how this import resolves its dependencies. Done means the example builds without the missing-module error.

Written by the indexing model from the issue text.

Description

Getting error on next project: Module not found: Can't resolve 'yaml'

import { RedocStandalone } from 'redoc';

export default function RedocComponent({ apiSpecs }: { apiSpecs: any }) {
return (
    <RedocStandalone
      spec={apiSpecs}
      options={{
        theme: theme === 'dark' ? redocDarkTheme : redocLightTheme,
        hideDownloadButton: true,
        expandResponses: '200,201',
        requiredPropsFirst: true,
        sortPropsAlphabetically: true,
        showObjectSchemaExamples: true,
        nativeScrollbars: true,
        pathInMiddlePanel: true,
      }}
    />
  );
}
Image
Dominant language
TypeScript
Stars
25.9k
Forks
2.4k
Avg merge
13h 10m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Redocly/redoc

All issues in Redocly/redoc

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.