Maybe a convention between hosts to prefix an import with an integrity
check?
``` js
import foo from 'sha1sum:ef70d15a0700d2108e0df27dde750f5c682b4697!./foo.js';
```
It looks kinda of dirty, but the specification allows it (aside from the
colon character that is forbidden right now)
This types of
Hi,
> The problem with inlining the integrity into every import site is that this
> is naturally incompatible with import maps.
I don't see a problem with that. When using import maps, you should be
able to specifiy the integrity check in the import map, not needing it
in the module itself.
When
The problem with inlining the integrity into every import site is that this
is naturally incompatible with import maps.
On Sat, 1 Aug 2020 at 08:57, Jordan Harband wrote:
> That seems like something that could possibly be achieved via
> https://github.com/tc39/proposal-import-assertions
>
> On
That seems like something that could possibly be achieved via
https://github.com/tc39/proposal-import-assertions
On Sat, Aug 1, 2020 at 1:15 AM Michaël Rouges
wrote:
> Hi all,
>
> As proposed a year ago on an old repository (thanks to ljharb, noticed me
> that fact), on the browser side, the
Hi all,
As proposed a year ago on an old repository (thanks to ljharb, noticed me
that fact), on the browser side, the integrity check should be controllable
**for each imported module**. Actually, it's just impossible to do it
without bundling.
5 matches
Mail list logo
