https://github.com/devlato/proposal-from-import

Proposal for Python-like import syntax extension
https://github.com/devlato/proposal-from-import

ecmascript ecmascript-proposal ecmascript-syntax es6 es7 esnext javascript proposal proposals

Last synced: 17 days ago
JSON representation

Proposal for Python-like import syntax extension

• Host: GitHub
• URL: https://github.com/devlato/proposal-from-import
• Owner: devlato
• Created: 2018-04-17T15:37:15.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-04-20T09:13:16.000Z (almost 7 years ago)
• Last Synced: 2024-11-22T11:32:12.624Z (3 months ago)
• Topics: ecmascript, ecmascript-proposal, ecmascript-syntax, es6, es7, esnext, javascript, proposal, proposals
• Size: 4.88 KB
• Stars: 2
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# proposal-from-import

Proposal for Python-like import syntax extension

## Example

```javascript

from 'module' import defaultExport;

from 'module' import { export1, export2 [, ...] };

from 'module' import defaultExport, { export1, export2 [, ...] };

from 'module' import defaultExport, { export1 as alias1, export2 as alias2 [, ...] };

from 'module' import defaultExport, { export1, export2 as alias2 [, ...] };

from 'module' import defaultExport, * as moduleName;

```

## Motivation

The [specification](https://www.ecma-international.org/ecma-262/6.0/#sec-imports) says that currently proposed syntax means static code import. 

The actual module code is being imported before any code runs. 

This approach gives ample possibilities for performing static checking. That's why advanced autocompletion features are possible.

But with current syntax it's not convinient to use the autocompletion features at all. 

Until user typed a module name, a text editor cannot deduct what to complete.

So developer has to type at least `import from 'module'` and start typing braces after `import` word then to get autocompletion running. It doesn't feel so much convenient. 

The Python-like syntax `from 'module' import ...` feels more organic way to import using autocompletion. So here comes this proposal to add support for this syntax too. The examples provided below show the main difference.

In this first example a developer has to type everything else before actually typing exported field names to get autocompletiong running.

```javascript

import { Component } from 'react';

```

In the second example a developer could just type an import statement in an organic left-to-right way. An editor will be able to identify the module name even before typing an opening brace, so autocompletion will run when expected.

```javascript

from 'react' import { Component };

```

## So... you want this instead of import ... from?

No. The proposal offers this syntax as an alternative to `import ... from` syntax, but not as a replacement. The semantics of this syntactical extension is totally the same as of usual `import ... from`.