Skip to content
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

PR: Tracking progress for later alignment with web-modules. #598

Open
1 of 2 tasks
lemanschik opened this issue Dec 5, 2022 · 2 comments
Open
1 of 2 tasks

PR: Tracking progress for later alignment with web-modules. #598

lemanschik opened this issue Dec 5, 2022 · 2 comments

Comments

@lemanschik
Copy link

This can be ignored by the most people you will see it soon in your editor. and browser without any intervention needed this is a internal engineering change nothing big to worry about.

es4x issues

Overall Tracking

@pmlopes
Copy link
Contributor

pmlopes commented Dec 7, 2022

Parsing and look up is complete, the final step is how to register the source maps. This means that the file system resolver needs to issue events whenever a file is read to attempt to load the map if present.

@lemanschik
Copy link
Author

lemanschik commented Dec 7, 2022

@pmlopes

import('./resolverIdHook.js?id=myModuleSpecifier').then((resolvedId)=>import(resolvedId));
// This defines what happens 
const importObject = { imports: { imported_func: (arg) => console.log(arg) } };

WebAssembly.instantiateStreaming(fetch("simple.wasm"), importObject).then(
  (loadedInMemory) => loadedInMemory.instance.exports.exported_func()
);

import maps get executed on a other layer they get static into mem no need to look at it after instantiation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants