Babylon master fails npm install

Bugs
1

hello kind folk! i’m picking up babylon because i’m interested in doing work to improve its compatibility and possibly simplify its build system. however, i immediately encountered this error, and figure there must be some mistake i’m making:

  1. i did a fresh clone of babylon from github
  2. running npm install fails, while sitting on the latest master commit bfdfdab7a13bd22915c0eca320f08a61cb560d8d

i thought this was strange, considering the azure pipeline suggests the nightly build succeeded? i’m getting this error:

chase@ragnarok-vm:/work/Babylon.js$ npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: babylonjs@5.0.0-alpha.12
npm ERR! Found: typescript@4.2.3
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"^4.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"^2.7 || ^3" from awesome-typescript-loader@5.2.1
npm ERR! node_modules/awesome-typescript-loader
npm ERR!   dev awesome-typescript-loader@"^5.2.1" 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! 
npm ERR! See /home/chase/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/chase/.npm/_logs/2021-03-05T09_54_59_231Z-debug.log

is there something on my end that i’m not thinking about? i wanted to ask about this here, before i creating a github issue about this. thanks!

2

i filed a github issue about this: npm install fails on master · Issue #10024 · BabylonJS/Babylon.js · GitHub

i’m very excited to do some work on babylon!

3

Adding @sebavan

4

@chase-moskal, did you follow this guide ? Start Contributing to Babylon.js | Babylon.js Documentation

This is really strange as it all work on the CI servers who starts from clean install.

5

Once you include the babylonjs npm library through npm install how do you gui filepath so npm doesn’t find anything there, so the second import fails .