Closed loynoir closed 1 year ago
Subresource Integrity
deno
node
Now, there is ESM. I think there should have a concept update combine two, in flavor of each dependency manager reinvent different lock file.
"imports": {}, "scopes": {}, "integrity": {} | ./lock/file/relative/path/to/import/map,
As ESM system differ from legacy system, I think, should iter into the inner most dependency, and update field integrity or file flatly.
https://github.com/nodejs/node/issues/44830
.integrity
Array<Record<string,string>>
importId
Background
Subresource Integrity
for old days javascript.deno
support import map, and invent own lock file.node
not yet support import map.Feat
Now, there is ESM. I think there should have a concept update combine two, in flavor of each dependency manager reinvent different lock file.
Additional
As ESM system differ from legacy system, I think, should iter into the inner most dependency, and update field integrity or file flatly.
Related
https://github.com/nodejs/node/issues/44830
Thoughts
.integrity
as a url. Maybe user can store their import map in their dotfile repo?.integrity
as anArray<Record<string,string>>
, and whenimportId
not uniq, throw error.