How to add custom import attributes? (to test polyfill ideas)

[trusktr]

Over in

• How to polyfill custom module type? trusktr/element-modules#2

I'd like some pointers on how to add a custom import attribute before jumping in, so I can make concepts (polyfills) of what new features could look like.

In this case, I want to prototype what "element modules" or "html modules" could look like as part of the Web Components CG.

[guybedford]

As a polyfill project, the best way to add a new polyfill to ES module shims for this would be to create a fork and.

Basically, following the existing pattern for JSON and CSS in the source code, it would be possible to extend the project to polyfill other features.

If these features were to achieve placement in a standardization process, we can definitely upstream them into the project as it does aim to support polyfilling all web standards.

Pluggable attribute systems is not a goal for the project though, which might explain the friction you're hitting. But forking is exactly the recommended way here since it's a feature addition to the project.