How should this interact with tools?

[littledan]

JS build tools may be another place where module attributes could be given meaning. Would this be useful? Desirable for the ecosystem? Cc @jhnns @sokra @guybedford @xtuc @lukastaegert

[xtuc]

Reposting my comment here:

I think another use case would be for tooling; transpilers could tune their code generation based on attributes for instance:

import {a} from "b" with parserPlugin: 'jsx';

or a bundler using loaders:

import {a} from "b" with loader: 'babel';

or bundlers using multiple loaders for the same type but not the same runtime representation:

import img from "./my_resource" with type: "image", as: "json";

This proposal allows arbitrary keys so it could be anything.

[JLHwung]

Bundlers use multiple loaders with configurations:

import Styles from "./styles.css" with loaders: [
  { loader: "style" },
  { loader: "css", options: { modules: true } }
];

The example is taken from Webpack Loaders Doc.

[xtuc]

The syntax is being discussed in #6 #3 #12, but it will likely only allow primitive types.

[littledan]

This isn't the first time I've heard the idea of JSON-like data in module attributes. It might be worth more consideration.