Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document the inanity of supporting Node.js 10 #86

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document the inanity of supporting Node.js 10 #86

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,18 @@ namespace like `mything.SomeType`.
But in almost all cases, it's much simpler to just use named
exports exclusively.

## Very Old Module Resolution Algorithms

Before Node.js v12 and in some other old module resolution
implementations the exports field is not respected, making it
impossible to load CJS code with require and ESM code with
import.

The entire point of tshy is to build hybrid (ESM and CJS)
packages. tshy does not and never will support targeting
platforms like Node.js v10 that do not respect the package.json
exports field.

## Configuration

Mostly, this just uses opinionated convention, and so there is
Expand Down
Loading