Interface CommonPluginData

specifies the original namespace of the link/path that is being transformed/resolved by one of our plugins.

this is needed because once a path is loaded (via esbuild.PluginBuild.onLoad | build.onLoad) in a certain namespace, any dependency paths of it will inherit the same namespace, and esbuild will only look for a resolver (i.e. esbuild.PluginBuild.onResolve | build.onResolve) that has its namespace set to the inherited namespace.

thus, to exit out of this namespace loop, we need this piece of information in order to restore the namespace back to the original, before one of our plugins' resolver captured it.

you may ask why would we want to exit out of our plugin's namespace? and that is because it would give other external plugins the chance to resolve the paths, should they have a correct filter for it (i.e. it is non-invasive). moreover, it would allow us to use a multitude of different namespaces for each of our own plugins, with no need for a hidden layer of collaboration between them.

specifies the current scope's import-map aliases (which is usually just the global import-map).

these will need to be checked by the "unresolver" function to make sure that we don't exit out of our namespace, while being asked for resolving the path that is part of the current scope's import map.

the keys of this object hold the aliased name of the import, while the values hold the absolute path of the referenced resource.

for further reading on import maps, see ImportMap.

specifies the current scope's runtime package manager (such as deno, jsr, npm, node, etc...), so that the package's own import and export aliases can be resolved appropriately.