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

No named exports found in module #863

Closed
matthieusieben opened this issue Apr 19, 2017 · 6 comments

Comments

@matthieusieben
Copy link

commented Apr 19, 2017

// File a.js
export const A = 'a'

// File b.js
export * from './a.js'

// File c.js
export * from './b.js'
standard c.js

Will result in No named exports found in module './b.js' import/export

@feross

This comment has been minimized.

Copy link
Member

commented Apr 22, 2017

In a fresh folder, I cannot reproduce this issue. Is it possible that you're using webpack and this rule is using that configuration?

@rbecheras

This comment has been minimized.

Copy link

commented Dec 28, 2017

@matthieusieben I got the same issue. Could you explain the solution please ?

@rbecheras

This comment has been minimized.

Copy link

commented Dec 28, 2017

Ok I found the solution.

Don't:

// File c.js
export * from './b.js'

Do:

// File c.js
export default b from './b.js'
@TriMoon

This comment has been minimized.

Copy link

commented Dec 28, 2017

@rbecheras, you DO understand that those two export styles do NOT function the same right?

@timoxley

This comment has been minimized.

Copy link
Contributor

commented Dec 29, 2017

@TriMoon perhaps explain the difference

@TriMoon

This comment has been minimized.

Copy link

commented Dec 30, 2017

@timoxley export@mdn does a much better job at that as i should 😉

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

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