# Local Documentation Build Errors

**URL:** <https://forum.babylonjs.com/t/local-documentation-build-errors/30010>\
**Category:** Questions\
**Created:** [May 4, 2022, 8:10am UTC](https://forum.babylonjs.com/t/local-documentation-build-errors/30010 "2022-05-04T08:10:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnK](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/johnk/32/26764_2.png) [@JohnK](https://forum.babylonjs.com/u/JohnK)\
**Post date:** [May 4, 2022, 8:10am UTC](https://forum.babylonjs.com/t/local-documentation-build-errors/30010/1 "2022-05-04T08:10:03Z")

</div>

@RaananW suggestions please to resolve the following

I pulled the latest version of the documentation

After ‘yarn dev’ I got

```auto
yarn run v1.22.11
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - automatically enabled Fast Refresh for 1 custom loader
event - compiled client and server successfully in 1947 ms (617 modules)
wait - compiling /404 (client and server)...
event - compiled client and server successfully in 1188 ms (682 modules)

```

On entering ’ [http://localhost:3000/](http://localhost:3000/)’ in the browser (both firefox and edge) I got

```auto
wait - compiling / (client and server)...
wait - compiling /404 (client and server)...
error - ./pages/[...id].tsx:193:29
Module not found: Can't resolve 'remark-gfm'
  191 | const props = await getPageData(params.id, true);
  192 | const remarkSlug = (await import("remark-slug")).default;
> 193 | const remarkGfm = (await import("remark-gfm")).default;
      | ^
  194 | props.mdxContent = await serialize(props.content, {
  195 | mdxOptions: {
  196 | remarkPlugins: [remarkSlug, /*remarkLint, */ remarkGfm],

Import trace for requested module:
./pages/index.tsx

https://nextjs.org/docs/messages/module-not-found

```

I updated NPM and when I tried ‘npm install’ I got

```auto
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: documentation@0.1.0
npm ERR! Found: typescript@4.4.4
npm ERR! node_modules/typescript
npm ERR! dev typescript@"~4.4.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"3.9.x || 4.0.x" from typedoc@0.19.2
npm ERR! node_modules/typedoc
npm ERR! dev typedoc@"^0.19.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

```

versions used are  
node 16.13.2  
npm 8.8.0  
yarn 1.22.11  
tsc 4.6.4

---

<div class="post-metadata">

**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\
**Post date:** [May 4, 2022, 9:47am UTC](https://forum.babylonjs.com/t/local-documentation-build-errors/30010/2 "2022-05-04T09:47:39Z")

</div>

make sure to run `yarn install` to install all missing dependencies

---

<div class="post-metadata">

**Author:** ![JohnK](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/johnk/32/26764_2.png) [@JohnK](https://forum.babylonjs.com/u/JohnK)\
**Post date:** [May 6, 2022, 8:17am UTC](https://forum.babylonjs.com/t/local-documentation-build-errors/30010/3 "2022-05-06T08:17:16Z")

</div>

is there anyway that on running yarn dev that, when necessary, a simple message such as ‘an update to yarn x.x.x, npm x.x.x and re-install is required?’

The same idea on npm run … for Babylon.js compilation?

---

<div class="post-metadata">

**Author:** ![RaananW](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/raananw/32/28955_2.png) [@RaananW](https://forum.babylonjs.com/u/RaananW)\
**Post date:** [May 6, 2022, 10:12am UTC](https://forum.babylonjs.com/t/local-documentation-build-errors/30010/4 "2022-05-06T10:12:50Z")

</div>

Your IDE (like vscode) can warn you of a dependency is missing, but not if your version doesn’t match the lock file’s version. I usually know when the dependencies have updated so i update yarn or npm when needed, but i agree that it would be nice to be notified
