Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upNo named exports found in module #863
Comments
This comment has been minimized.
This comment has been minimized.
|
In a fresh folder, I cannot reproduce this issue. Is it possible that you're using webpack and this rule is using that configuration? |
feross
added
the
need more info
label
Apr 22, 2017
matthieusieben
closed this
Apr 27, 2017
This comment has been minimized.
This comment has been minimized.
rbecheras
commented
Dec 28, 2017
|
@matthieusieben I got the same issue. Could you explain the solution please ? |
This comment has been minimized.
This comment has been minimized.
rbecheras
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' |
This comment has been minimized.
This comment has been minimized.
TriMoon
commented
Dec 28, 2017
|
@rbecheras, you DO understand that those two export styles do NOT function the same right? |
This comment has been minimized.
This comment has been minimized.
|
@TriMoon perhaps explain the difference |
This comment has been minimized.
This comment has been minimized.
TriMoon
commented
Dec 30, 2017
|
@timoxley export@mdn does a much better job at that as i should |
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.
matthieusieben commentedApr 19, 2017
Will result in
No named exports found in module './b.js' import/export