Setup with .Net Core and LibMan

Hi everyone,

Is it possible to setup a BabylonJs project in .Net Core with the use of LibMan instead op NPM?
I have tried several configurations but no luck :wink:

In this case I get build errors: Cannot find name "WebGLObject:.


“version”: “1.0”,
“defaultProvider”: “unpkg”,
“libraries”: [
“library”: “@types/jquery@3.5.4”,
“destination”: “wwwroot/lib/types/jquery/”
“library”: “@types/sizzle@2.3.2”,
“destination”: “wwwroot/lib/types/sizzle/”
“library”: “@babylonjs/core@4.2.0”,
“destination”: “wwwroot/lib/babylonjs/core/”


“compileOnSave”: true,
“compilerOptions”: {
“noImplicitAny”: false,
“noEmitOnError”: true,
“removeComments”: false,
“noResolve”: false,
“sourceMap”: true,
“preserveConstEnums”: true,
“resolveJsonModule”: true,
“target”: “es6”,
“outDir”: “wwwroot/js”,
“typeRoots”: [ “./wwwroot/lib/types” ],
“module”: “commonjs”,
“lib”: [
“types”: [
“include”: [

Thnx in advance

Adding @RaananW and @sebavan who may know what .Net Core and LibMan are!

WebGLObject is defined in TypeScript’s lib.dom.ts, so it seems like libMan doesn’t read TypeScript’s lib files. Or that the version of those typings is so old that it doesn’t include this object. But this is very far fetched. What version of typescript are you using? And can you confirm that other DOM features are supported? My guess is that this is the first of many missing object is has (most of the WebGL context objects, HTMLCanvasElement, those are all defined in the same lib file)


Thnx for the input!
You’re right. The typescript fib files (4.2.4) aren’t read.

I would would have liked to use LibMan because of my inexperience with npm, webppack eslint and all the settings that come with it.

But my guess is that the use of npm is the most preferred way. Am I right?

I can tell you that npm works well :slight_smile:

The lack of libs mean that the typescript compiler is ignoring the tsconfig.json file. I am not 100% sure it is libman’s fault. How are you compiling your project?

I can tell you that npm works well. Yarn as well. But I totally understand the need to use package managers that you know and trust. Check the typescript compilation process, it might be just missing a single parameter to make it work correctly.