Nowadays the package.json created by yarn generates the "main" entry point. I think could be a good (and necessary) idea to add "exports" entry.
The exports entry replaces/overwrites the "main" entry points and gives more control over what the package exposes or not.
Also, the "exports" entry is used to define subpackage settings in different situations as environments or platforms to use.
Nowadays the package.json created by yarn generates the "main" entry point. I think could be a good (and necessary) idea to add "exports" entry.
The exports entry replaces/overwrites the "main" entry points and gives more control over what the package exposes or not.
Also, the "exports" entry is used to define subpackage settings in different situations as environments or platform
Nowadays the package.json created by yarn generates the "main" entry point. I think could be a good (and necessary) idea to add "exports" entry.
The exports entry replaces/overwrites the "main" entry points and gives more control over what the package exposes or not. Also, the "exports" entry is used to define subpackage settings in different situations as environments or platforms to use. Nowadays the package.json created by yarn generates the "main" entry point. I think could be a good (and necessary) idea to add "exports" entry.
The exports entry replaces/overwrites the "main" entry points and gives more control over what the package exposes or not. Also, the "exports" entry is used to define subpackage settings in different situations as environments or platform