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

docs: fix small grammar errors #636

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

docs: fix small grammar errors #636

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
2 changes: 1 addition & 1 deletion docs/tips/defaultIsBad.md
View file
Original file line number Diff line number Diff line change
@@ -56,7 +56,7 @@ With `default` there is horrible experience for commonJS users who have to `cons
You don't get typos like one dev doing `import Foo from "./foo";` and another doing `import foo from "./foo";`

### TypeScript auto-import
Auto import quickfix works better. You use `Foo` and auto import will write down `import { Foo } from "./foo";` cause its a well defined name exported from a module. Some tools out there will try to magic read and *infer* a name for a default export but magic is flaky.
Auto import quickfix works better. You use `Foo` and auto import will write down `import { Foo } from "./foo";` because it's a well-defined name exported from a module. Some tools out there will try to magically read and *infer* a name for a default export but magic is flaky.

### Re-exporting
Re-exporting is common for the root `index` file in npm packages, and forces you to name the default export manually e.g. `export { default as Foo } from "./foo";` (with default) vs. `export * from "./foo"` (with named exports).