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

Per module-script tree information #148

Closed
Constellation opened this issue Aug 6, 2016 · 2 comments
Closed

Per module-script tree information #148

Constellation opened this issue Aug 6, 2016 · 2 comments

Comments

@Constellation
Copy link
Member

Constellation commented Aug 6, 2016

Looking through whatwg module spec and I think that the module-script assumes per-module-script-tree information. For example, nonce is propagated through the module script tree fetching.

However, in the current loader spec, it seems that BrowserLoader's @@fetch hook just takes the entry and the key. So the above information seems discarded through the pipeline. Is there any discussion to solve this?

Maybe, I misunderstand something. Please point it.

Personally, the easiest way to solve this issue is, instantiate BrowserLoader per script tag.
OR, passing metadata info throught the pipeline is one choise.

@caridy
Copy link
Contributor

caridy commented Aug 8, 2016

metadata was discussed here: #37, is that enough?

@Constellation
Copy link
Member Author

Looks nice. We need to discuss it in #37.

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

No branches or pull requests

2 participants