Skip to content

fix: typos #7

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.

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ the default export of the outer module. This can be written as:
export default from "mod";
```

This is symmmetric to the (existing) import form:
This is symmetric to the (existing) import form:

```js
import default from "mod";
Expand All @@ -191,7 +191,7 @@ to an existing lookahead restriction is necessary for supporting this case.

### Common concerns:

> Do we need this even through you can already do this with `export { default } from "mod"`?
> Do we need this even though you can already do this with `export { default } from "mod"`?

Yes! It is true that you can already "export from" a module's default export
without altering the local scope:
Expand All @@ -213,7 +213,7 @@ There is a benefit to this, it's explicit and it is symmetric with the
import { default as someIdentifier } from "mod"
```

However the purpose of this proposal is not to enable a new use case, the
However, the purpose of this proposal is not to enable a new use case, the
purpose is to provide an expected syntactic form which currently does not exist,
and which favors the "default" export.

Expand Down