à la carte vs buffet about import-maps HOT 5 CLOSED

Yep, that's included :). See https://github.com/domenic/package-name-maps#basic-url-mapping

from import-maps.

I'm not sure I quite understand, but did you see from the readme how a package already consists of multiple modules, only one of which is the main module? That should cover the many-module packages like lodash.

from import-maps.

I'm sure I'm the one who doesn't understand:

I just want to make sure than application developer can write in a JavaScript file that gets shipped to the browser, with this syntax:

import {isDate} from 'lodash/isDate.js';
import {isRegularExpression} from 'lodash/isRegExp.js';

That with the help of a package map, the browser will be able to make a single http request, to a single bundled file of the lodash library.

And to do so with a single configuration line, rather than one line per file.

from import-maps.

It looks like the referenced anchor #basic-url-mapping no longer exists.

In any case, I think that the feature being requested by @bahrus is not supported by the current proposal, if I understood his request well. What I think @bahrus is asking for is support for bundle files which include several distinct modules... However, the ES6 module format does not support such thing as an inline modules, which would make it possible to ship several modules in a single file.

What import maps support is mapping several sub-modules of a package by mapping only a single base entry, as explained in packages via trailing slashes.

from import-maps.

Ah, yes, packaging up multiple files into one file is not part of import maps. Instead, check out https://github.com/WICG/webpackage.

from import-maps.