Wes Todd

@Qard Where is the best place for us to engage on the proposal for unified hooks and this feature?

I commented in the meeting that much usage of these api's probably comes from a handful of fs wrapper libraries. To follow up on those, here are the most popular...

Only slightly related, but it might also be helpful if there were best practices or shared approaches we could take for encrypting/decrypting these so they are not just plain text...

@ljharb Added an open question at the end with my concern: > it would superseded all the work currently being done on yarn pnp and npm 8. If we let...

> I don’t think it would supersede it - they’d just get to provide an import map instead of their current approach, whenever it became available. Perhaps @arcanis can weigh...

> Amazing to see this work, thanks @wesleytodd for investigating. Thanks for responding on twitter and sending me down this path :) > For example, with conditional exports, the same...

> Does --experimental-loader make this possible already? For testers npm i wesleytodd/import-map-loader would be easier than rebuilding node.js. That is really how I am testing it today. If you check...

> Given the large uncertainty, it seems premature to me to even signal a possible future core implementation when there may be none at all. Where can we look to...

> The new package.json "exports" implements a lot of the same functionality, It is a bit different. The goal of an import map is that tooling can do creative things...

> If we saw some interest in import maps beyond the current browser heavy path forward to address things like those in this issue such as having more data, composition...