Direct export throws SyntaxError about fuse-box

[nchanged]

Okay, are you sure that App has default exports? Cuz if it does not, you will get this error

Even my vscode complains on the syntax above.
try

export { App } from './App';

[msuntharesan]

Yes it does. see fork

[nchanged]

It says Declaration or statement expected

[msuntharesan]

Sorry about that. Fixed the import. Still same error

[nchanged]

If acorn complains that means that you have a syntax error

[devmondo]

@VanthiyaThevan is it possible that you are using some feature that needs some babel plugin, or you are just using the original repo code?

[eisisig]

I'm actually getting this error (Unexpected token) and error reporting from acorn really doesn't help.

[devmondo]

@VanthiyaThevan i checked the project,

first there is syntax error here react example
cons should be const
also
export App from './App';
should be
export { App } from './App';

after i fixed those, build is passing fine, hope this helps

[nchanged]

Also please, make sure you references make sense
https://github.com/vanthiyathevan/react-example/blob/master/src/App/index.js#L1
You don't have App.js file in that folder.

[msuntharesan]

the difference to this working vs the the error
this throws error

export App from './App'

This compiles as expected.

import App from './App'
export { App };

@devmondo It is possible. I've switched to using presets latest, stage-0, and react and explicitly added transform-export-extensions. Still same acorn error.

[devmondo]

@VanthiyaThevan thanks for update,

can you try this export {App} from './App' directly without import statement.

[msuntharesan]

@devmondo
Hmm interesting. export {App} from './App' works. But given the ./App is default export, Shouldn't export App from './App' be working?

[nchanged]

export App from './App' is not a valid syntax.
Please. read up here

[msuntharesan]

I see now. the syntax I am using are part of proposal

• https://github.com/leebyron/ecmascript-export-default-from
• https://github.com/leebyron/ecmascript-export-ns-from

and stage 1 supported by babel and not by acorn.
see the astexplorer.net

• bable
• acorn

[nchanged]

I see. I think we can use babel AST as an alternative.
Required:

• A way to bypass acorn parse and use AST provided by other sources. (for example by babel-plugin)

[nchanged]

1.3.13 has it fixed. stage-0 does not spit an error, however, is not giving me expected code back.
It transpiles it as "undefined". So it must be related to that plugin. Nonetheless, all questions to babel.

[msuntharesan]

Thanks for the quick response. But if I specify my own test without limit2project this reverts to using only acron AST only because of This

[nchanged]

Sorry, my bad. FIxed in v1.3.15

[devmondo]

i can confirm that Error reporting in v1.3.16 is awesome now!!!

[nchanged]

Nice! @devmondo Thanks,
Let's wait for @VanthiyaThevan to confirm that BabelPlugin is now using babel AST instead of acorn.

[msuntharesan]

Thanks. This works. Yes the error message is very cool. Will try it on a real project and let you know.
The undefined is because of babel transpiling.
Although when export is pointing to a non existing file, The transpiling goes through without errors. May be it should warn the file doesn't exist?

[nchanged]

Hi!
Thanks!
Certainly a warning can be optional. But in essence, a user might require a file that's not in a bundle. And get it via dynamic imports. So this has to be though through.

Thanks again for submitting this issue, it led to an amazing improvement on BabelPlugin and the core itself.

Cheers.

[msuntharesan]

Thanks. I'm going to try this on a fairly large project.