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
Can it be useful to add importer informations on import.meta for better logs (and errors without checking all stack trace) ? For instance, a multiple times imported module can log contextualized messages (eg.: in version checker to indicate which module require a specific version ).
For main module, importer should be set to null
Maybe Deno.mainModule should be moved (or duplicate since import.meta is not accessible outside of modules, eg: REPL) to
import.meta.mainModule={url: '...',main: true,importer: null//maybe undefined or refers to itself}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Can it be useful to add importer informations on import.meta for better logs (and errors without checking all stack trace) ? For instance, a multiple times imported module can log contextualized messages (eg.: in version checker to indicate which module require a specific version ).
Maybe it can be recursive to get imports chain for some usages
For main module, importer should be set to
nullMaybe Deno.mainModule should be moved (or duplicate since import.meta is not accessible outside of modules, eg: REPL) to
Beta Was this translation helpful? Give feedback.
All reactions