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.

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

"Export from" Unexpected token #847

Closed
pinn3 opened this issue Apr 8, 2017 · 2 comments

Comments

@pinn3
Copy link

commented Apr 8, 2017

Using babel export extensions you get "Parsing error: Unexpected token".

Example:

// components/index.js
export Header from './header.js'
export Footer from './footer.js'

// produces "Parsing error: Unexpected token Header"
@falmar

This comment has been minimized.

Copy link
Contributor

commented Apr 9, 2017

I may be wrong. But I think this is on the ESLint side capabilities to understand the feature

Take a look if this will be a workaround for you. #652

@feross

This comment has been minimized.

Copy link
Member

commented Apr 9, 2017

This is a stage 1 proposal and not part of the spec yet. You need to tell standard to use babel-eslint as your parser. See https://standardjs.com/#how-do-i-use-experimental-javascript-es-next-features

@feross feross closed this Apr 9, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
3 participants
You can’t perform that action at this time.