# Bringing import maps to JS: \`import "./importmap.json" with { type: "importmap" }\`?

**URL:** <https://es.discourse.group/t/bringing-import-maps-to-js-import-importmap-json-with-type-importmap/2481>\
**Category:** 💡 Ideas\
**Tags:** proposal\
**Created:** [January 4, 2026, 6:51pm UTC](https://es.discourse.group/t/bringing-import-maps-to-js-import-importmap-json-with-type-importmap/2481 "2026-01-04T18:51:35Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![bakkot](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/bakkot/32/22_2.png) [@bakkot](https://es.discourse.group/u/bakkot)\
**Post date:** [January 7, 2026, 11:35pm UTC](https://es.discourse.group/t/bringing-import-maps-to-js-import-importmap-json-with-type-importmap/2481/10 "2026-01-07T23:35:24Z")

</div>

Web platform import maps can in fact define define specifiers which would otherwise be resolvable. That’s my point. Something like `from "foo"` is never resolvable (… I think) but `from "./foo"` is resolvable in the absence of an import map and can be defined as something else by an import map as long as the import map is added before that import.

---

_[View the full topic](https://es.discourse.group/t/bringing-import-maps-to-js-import-importmap-json-with-type-importmap/2481)._