Possible boolean value

[guybedford]

I've just been working out the interaction here with the "mode" spec ideas, and one thing that comes up then is that if we do allow the "main" to point to ".mjs" files, would we want "exports" to be able to be an empty object to get encapsulation:

{
  "main": "main.mjs",
  "exports": {}
}

A simpler form of the above might be just:

{
  "main": "main.mjs",
  "exports": false
}

where it is clear that is then a "frozen" package as it were.

It only really makes sense if the main field is kept with the mode proposal, but thought we should discuss it here first.

[jkrems]

Setting exports to false should work now and we have a test for it.

[ljharb]

(specifically, Object.assign/Object.keys semantics will be used, so any value without enumerable keys will be the same as {}, including false)

[SMotaal]

@ljharb Just to clarify… we're talking here about { "exports": false } not { "exports": "false" } as per op text, right?

The latter would assign/key as { 0: "f" … 4: "e" }… right?

[ljharb]

The former, yes. The latter is a valid string value for the field.

[SMotaal]

@guybedford do we want to revise the op text to read { "exports": false } not { … "false" } avoid confusion?

[guybedford]

Sure, have done that.