e.g. put it into Assets/MyPackages~/MyPackage
Ok makes sense - there might be a bug then. Iāll try to reproduce it
Just to make sure, I donāt want to move the utils package into the unity project
by user 725499871615909899
Yes thatās fine. Iāll take a look at this tomorrow and let you know. It should work with linking to the package from the npmdef
cool thanks, keep me posted ![]()
by user 725499871615909899
Can you try again using the latest version?
yup will do
by user 725499871615909899
still getting the error
by user 725499871615909899
Can you send me the npmdef asset ?
by user 725499871615909899
Thanks
This seems to be a new issue in 2022.3 - im getting the warning flood as well in later versions now.
@herbstā:cactus: Hallo Felix, hatte Dir ein Mail in Twitter (neuerdings X
geschrieben, weiĆ nicht, ob Du das noch benutzt. Die für mich wichtige Frage war, ob ich Deinen mofifizierten USDZ-Exporter für mein Projekt nutzen kannā¦
GrüĆe, Max Eichner
by user 652771179035230210
Hey, falscher Channel, schick mir gerne ne DM oder mach ne neue Frage in #needle-engine-questions auf - danke
Hello @Alex Gomes could you update to 3.22.3 and try it again? Thank you ![]()
will try now
by user 725499871615909899
Maybe Iām doing something wrong
by user 725499871615909899
- Create ExternalPackages in Assets/
- Create NPM Definition (Link to external packaged)
- Select typescript package āutilsā from monorepo in finder
- Rename New NpmDef to Utils
- Install in Project āNeedle/new projectā
by user 725499871615909899
Have you tried removing it and adding it again in ExportInfo? Can you check the dependencies array above?
