-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some relative module imports fail in preload with Module "(path)" not found!
#1373
Comments
The XS linker ( We've got a fix for that which works for your test case. The changes will be in the next repository update. If you want to try them sooner, here's the updated source code
Note: the example's manifest preloads "root/main". That causes "root/#another" to be preloaded too, so it executes the traces at link time (you will see them as part of the build output). To make the test do something meaningful at runtime, preload "root/#another" instead. |
All my private modules preload - totally awesome. Thanks! |
Build environment: Windows
Moddable SDK version: Latest released
Target device: Win, ESP32
Description
Another path resolution issue similar to #1372, but this time with preload. It appears that preload is unable to resolve some relative module loads using the private-scope style (
root/#module/...
). I've found that it works with..\myfile.js
but not..\..\myfile.js
, such as "import { xyz } from "../../myfile.js";" where it reportsModule "../../myfile.js" not found!
.See this repo for a small demo of the problem. If you remove the preload, the module runs fine, but with the preload the build fails with:
Steps to Reproduce
mcconfig -m -d
and see the preload failuremanifest.json
The text was updated successfully, but these errors were encountered: