Open guybedford opened 5 years ago
Here is a suggested path for supporting "exports" in Node.js (//cc @jamiebuilds, @devongovett):
"exports"
['node', 'esmodule', 'main']
My concern with the above is managing the list of conditionals requires some coordiation between environments.
Therefore I see the prerequisite for such a proposal as a central website / repo where we can coordinate on these names.
So I'd like to propose a new repo and website for managing this process and these proposals.
Does that seem a sensible approach moving forward?
Here is a suggested path for supporting
"exports"in Node.js (//cc @jamiebuilds, @devongovett):['node', 'esmodule', 'main']in that order of precedence."exports"is an object it will aim to perform the above selection in that precedence order for"exports".My concern with the above is managing the list of conditionals requires some coordiation between environments.
Therefore I see the prerequisite for such a proposal as a central website / repo where we can coordinate on these names.
So I'd like to propose a new repo and website for managing this process and these proposals.
Does that seem a sensible approach moving forward?