error with es-pack-js when executing 'npm i' about three-geo HOT 15 CLOSED

Apologies. my mistake. I had skipped a step and VScode wasn't fully hooking into WSL when I booted the project.

Fixed it, and it's all working fine under WSL2 as per your original docs (after installing node etc as per MS instructions above).

Thanks for the help, sounding board helps troubleshoot. Sorry to bother you, but at least you can add some extra instructions perhaps for WIndows users now to use WSL. Microsoft actually recommends this for js development now anyway, so all good.

Looking forward to having a play with it, some great work you've done there!

You might be interested in what I want to add actually, could be a useful addition.
Haven't done three.js for a while so kind of starting from scratch again.

from three-geo.

Have you solved the problem yet？I ran into the same problem

from three-geo.

Same here, can't get the example running locally

from three-geo.

To my knowledge, this error happens when building on Windows.

Using the latest es-pack-js (v0.5.3 with partial Windows support) might help:

$ npm config set script-shell bash
$ npm i [email protected]
$ npm run build

Updates (2022-03-22): As of 36f0862, building three-geo on Windows should just work by

$ npm config set script-shell bash
$ npm run build

from three-geo.

yes, I'm working on Windows.

I've tried your proposed solution and got this error on the second command:

from three-geo.

Hello.

Windows user here, same error.

npm run build

[email protected] build
es-pack build -m umd

/bin/bash: es-pack: command not found

Any clues?

from three-geo.

/bin/bash: es-pack: command not found

Try npm i first?

from three-geo.

Yes, already did fails.
Tried npm i [email protected] and fails.

Switching to WSL.

from three-geo.

Yes, already did fails. Tried npm i [email protected] and fails.

Please try npm i [email protected] (latest version 0.5.13, not 0.5.3). Still fail?

from three-geo.

I switched to WSL2, installed nvm, node etc according to https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl

All checks out, everything installed. Opened Geo in VScode in WSL via code .

Try npm i or npm i three-geo but it fails now on: npm ERR! /bin/bash: node: command not found

But node is installed.

node --version
v18.12.1

from three-geo.

I switched to WSL2, installed nvm, node etc according to https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl

All checks out, everything installed. Opened Geo in VScode in WSL via code .

Sorry, I am not familiar with the Windows environment...

FYI - latest CI build on Windows (via GitHub Action's Docker) https://github.com/w3reality/three-geo/actions/runs/4459639864/jobs/7832217785

from three-geo.

@sonicviz I have added some notes regarding this.

Thanks for your interest, and looking forward to seeing enhancements!

from three-geo.

No problem.

Q: How do you calculate terrain height relative to the position units in three.js, which are also dependant on the zoom factor?

For example, if I want to position an object 1m above sea level (which according to https://docs.mapbox.com/data/tilesets/guides/access-elevation-data/#mapbox-terrain-rgb sea level is 0) how do I translate that into a relative mesh position,z value that will translate it a unit of 1m (or 10m or whatever) relative to the scale of the mesh terrain elevation?

Also. how does that position calculation change based on the zoom factor, which can be from 11 to 17?

from three-geo.

Q: How do you calculate terrain height relative to

Okay, I think this is a different issue topic. Could you open a new thread?

from three-geo.

aok, done. ty

from three-geo.