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
Thanks for the fix, I can now update to latest.
After the update I still experience the issue which forced me to update in the first place, as I hoped it would have been fixed in later releases.
When I build on my machine it generates interfaces with physical path references:
In runtime they fail to work generating warnings:
I used webpack 3 and node 10.5, now using webpack 4 same node and tried webpack 4 with node 15. All the same.
The code is generated this way in both 0.1.35 and latest versions.
Is it known issue? What is the workaround? Is there a permanent fix?
UPD: more screenshots
expected - build result from another machine, 3rd pty developer:
I'm having an issue that production js contains phisical folder names for runtime-interfaces output.
I'm on version 0.1.35
Once I switch on 0.2.0 it generates error. It will generate the error even if I comment out the content of the source ts file
node node_modules/ts-runtime/bin/index.js src/app/glb/ts/runtime-interfaces.ts
The text was updated successfully, but these errors were encountered: