Comments (9)
Amendment: for the moment, I tried npm install --force
and got this list of warnings:
npm WARN using --force Recommended protections disabled.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/three
npm WARN three@"0.152.2" from the root project
npm WARN 5 more (n8ao, postprocessing, three-gpu-pathtracer, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer three@"^0.141.0" from [email protected]
npm WARN node_modules/three-bvh-csg
npm WARN three-bvh-csg@"0.0.5" from the root project
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/three
npm WARN peer three@"^0.141.0" from [email protected]
npm WARN node_modules/three-bvh-csg
npm WARN three-bvh-csg@"0.0.5" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/three-mesh-bvh
npm WARN three-mesh-bvh@"0.6.3" from the root project
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer three-mesh-bvh@"^0.5.13" from [email protected]
npm WARN node_modules/three-bvh-csg
npm WARN three-bvh-csg@"0.0.5" from the root project
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/three-mesh-bvh
npm WARN peer three-mesh-bvh@"^0.5.13" from [email protected]
npm WARN node_modules/three-bvh-csg
npm WARN three-bvh-csg@"0.0.5" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/webpack
npm WARN dev webpack@"5.76.0" from the root project
npm WARN 14 more (@statoscope/webpack-plugin, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer webpack@"^4.0.0" from [email protected]
npm WARN node_modules/ts-declaration-webpack-plugin
npm WARN dev ts-declaration-webpack-plugin@"1.2.3" from the root project
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/webpack
npm WARN peer webpack@"^4.0.0" from [email protected]
npm WARN node_modules/ts-declaration-webpack-plugin
npm WARN dev ts-declaration-webpack-plugin@"1.2.3" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/three
npm WARN three@"0.152.2" from the root project
npm WARN 5 more (n8ao, postprocessing, three-gpu-pathtracer, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer three@"^0.149.0" from [email protected]
npm WARN node_modules/web-ifc-three
npm WARN web-ifc-three@"0.0.125" from the root project
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/three
npm WARN peer three@"^0.149.0" from [email protected]
npm WARN node_modules/web-ifc-three
npm WARN web-ifc-three@"0.0.125" from the root project
from polygonjs.
... and npm run start
failed with (many mesages and finally)
webpack 5.76.0 compiled with 68 errors in 88841 ms
Thus, it seems to be more complicated to fix the dependency mismatch(es)
from polygonjs.
FYI: npm create polygonjs@latest
works better:
cd polygon-project && npm install
issues the following warnings:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/@polygonjs/polygonjs/node_modules/three
npm WARN three@"0.152.2" from @polygonjs/[email protected]
npm WARN node_modules/@polygonjs/polygonjs
npm WARN @polygonjs/polygonjs@"1.5.26" from [email protected]
npm WARN node_modules/polygonjs-editor
npm WARN 1 more (three-mesh-bvh)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer three@"^0.149.0" from [email protected]
npm WARN node_modules/@polygonjs/polygonjs/node_modules/web-ifc-three
npm WARN web-ifc-three@"0.0.125" from @polygonjs/[email protected]
npm WARN node_modules/@polygonjs/polygonjs
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/three
npm WARN peer three@"^0.149.0" from [email protected]
npm WARN node_modules/@polygonjs/polygonjs/node_modules/web-ifc-three
npm WARN web-ifc-three@"0.0.125" from @polygonjs/[email protected]
npm WARN node_modules/@polygonjs/polygonjs
but npm run polygon
works and starts up the editor...
from polygonjs.
Thanks a lot for the detailed error messages.
If you want to build the repo, I recommend to use yarn instead (so yarn
to install the dependencies, and yarn build
to build).
And if you want to start the editor, you can still use npm as you have with npm create polygonjs@latest
and npm run polygon
. That may not be clear yet (I still need to clarify that in the readme), but this repository only contains the main library, while the editor is not open source.
So if you want to use polygonjs via the editor, that's all you should need.
But if you want to develop against the main library, I do see like you errors when running yarn start
. I'll look into those shortly. But those don't happen when you export a scene via the editor, so they may or may not be a blocker depending on how you plan to use polygonjs.
from polygonjs.
I will try yarn asap
from polygonjs.
Ok,
so I cloned the PolygonJS repo again (from scratch) and yarn
ed. Despite of a few warnings, everything went fine:
yarn install v1.22.19
warning package.json: License should be a valid SPDX license expression
warning @polygonjs/[email protected]: License should be a valid SPDX license expression
[1/5] 🔍 Validating package.json...
warning @polygonjs/[email protected]: License should be a valid SPDX license expression
[2/5] 🔍 Resolving packages...
[3/5] 🚚 Fetching packages...
[4/5] 🔗 Linking dependencies...
warning " > @vue-reactivity/[email protected]" has unmet peer dependency "@vue/shared@>=3.0.0-rc.1".
warning " > [email protected]" has unmet peer dependency "ws@^8.5.0".
warning " > [email protected]" has incorrect peer dependency "three@^0.141.0".
warning " > [email protected]" has incorrect peer dependency "three-mesh-bvh@^0.5.13".
warning " > [email protected]" has incorrect peer dependency "three@^0.149.0".
warning " > [email protected]" has incorrect peer dependency "webpack@^4.0.0".
warning Workspaces can only be enabled in private projects.
[5/5] 🔨 Building fresh packages...
✨ Done in 24.42s.
from polygonjs.
You may think of explicitly recommending yarn
instead of npm
or (even better) completely remove any npm
examples
from polygonjs.
Yes, I'll put a warning in the docs and readme at the very least. But I still want polygonjs to be as framework/bundler agnostic as possible, so ideally projects scaffolded with yarn create polygonjs
or npm create polygonjs@latest
should work with both.
In the mean time, I've replaced webpack by vite for the dev build of polygonjs standalone, so yarn start
works again without errors. I'm unsure why webpack works in build but not dev, but vite has the additional benefit of being faster.
from polygonjs.
I've got npm
install working again. It looks like the reason it was failing was that one of the dependencies ( https://github.com/IFCjs/web-ifc-three ) was requiring an older version of threejs, and npm wasn't able to resolve that as well as yarn
. I don't fully understand how yarn/npm work under the hood, so the reason may be different, but removing this dependency ( and therefore refactoring how IFC is handled, see commit ) solved the problem for now.
from polygonjs.
Related Issues (20)
- animation/event system HOT 1
- Easily switch nodes to use workers HOT 2
- js builder HOT 1
- orbit controls ... HOT 2
- child node type 'geo' not found for node '/'. Available types are: , obj, root HOT 5
- assets creation and sharing HOT 1
- Clone methods do not respect proper OOP HOT 7
- Draco lib can't be installed HOT 6
- plugin system to create custom nodes HOT 1
- Update CSG to use manifold.js HOT 2
- wrong link in the docs HOT 5
- wrong "Local Export" path HOT 2
- "File > Save" does not work HOT 4
- How to import a scene into a plain HTML document? HOT 10
- "THREE.EXRLoader: provided file doesn't appear to be in OpenEXR format." HOT 4
- Run polygon.js as a webhook in response and return a message and an attachment HOT 7
- multiple rendering qualities HOT 1
- THREE's renderer and scene could be represented as nodes HOT 1
- light baking HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from polygonjs.