Missing "dynamic import wrapper" section in README about chrome-extension-tools HOT 3 CLOSED

Hi @micah-yeager, thanks for the heads up on the broken link! 👍

I just updated the link and added more information on the dynamic import wrapper.

Let me know what your think!

⭐️ Use ES2015 Modules In Your Scripts

Chrome extensions don't support modules in background and content scripts. We've developed a module loader specifically for Chrome extension scripts, so you can take advantage of Rollup's great code splitting features.

⭐️ How does the dynamic import wrapper work?

TLDR; RPCE parses the manifest and replaces any script path with an IIFE wrapper that loads the script using a dynamic import statement.

See Why do we need to use dynamic import in scripts? for the reasons we need dynamic imports.

Content scripts are pretty straight forward, and the wrapper they use is just an IIFE that loads the script and logs any import errors.

Background pages need a special wrapper because wake events (onInstalled, onMessage, etc...) fire before the import completes. We make sure we don’t miss any events by capturing all events that occur before the import promise resolves and then re-dispatch them after the import completes.

from chrome-extension-tools.

That makes a lot more sense. So am I correct in thinking that it doesn't need anything special to work out of the box, just use normal import statements in the background script?

from chrome-extension-tools.

@micah-yeager That's right! (sorry for the long delay)

from chrome-extension-tools.