You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if we just run npm pack,it doesnt include @babylonjs/core(in node_modules),just import it in dist/files
import { Engine, Scene, Color4, MeshBuilder, Vector3} from '@babylonjs/core';
at the same time, edit-axis-dialog doesn't have @babylonjs/core in node_modules.
If we run, edit-axis-dialog should show error message likeCan't resolve '@babylonjs/core' in .... .
There is two way can solve.
add @babylonjs/core in devDependency to edit-axis-dialog,then install.
copy widget's node_modules to edit-axis-dialog node_modules.
Does npm-pack-here consider this ?
In lerna,if using hosit, the @babylonjs/core maybe doesn't in widget's node_modules, but in its parent directory's node_modules.
Hi @Zaynex,
Not sure I totally follow you, so checking my understanding you have a lerna project setup like the following.
your-lerna-workspace/
package.json
packages/
widgets/
package.json (dependencies includes react and @bablonjs/core)
edit-axis-dialog/
package.json (dependencies includes widgets)
Is this correct? Could you be more specific about the problem you are running into with this setup?
I am not aware of anyone using npm-pack-here with lerna so not sure it will work for your situation, will need more specifics to be able to determine that.
Looking at your post to yalc, if the question is about if npm-pack-here supports locally testing mult-level transitive dependencies, then the answer is yes. To make it work you need to use the useGlobalCache option although be aware that there are some unsolved issues with it #10
Question
Hi, I am suffering from local node Dependencies debugging.I have some question.
The context of the question is based on this article
If
widget
package have a dependence like@babylonjs/core
,if we just run
npm pack
,it doesnt include@babylonjs/core
(in node_modules),just import it in dist/filesat the same time,
edit-axis-dialog
doesn't have @babylonjs/core in node_modules.If we run, edit-axis-dialog should show error message like
Can't resolve '@babylonjs/core' in ....
.There is two way can solve.
@babylonjs/core
in devDependency toedit-axis-dialog
,then install.widget's node_modules
toedit-axis-dialog node_modules
.Does
npm-pack-here
consider this ?In lerna,if using hosit, the
@babylonjs/core
maybe doesn't in widget's node_modules, but in its parent directory's node_modules.Additional Context
wclr/yalc#95 (comment)
The text was updated successfully, but these errors were encountered: