Can't import ES6 react module
up vote
0
down vote
favorite
Repro
https://github.com/jim-king-2000/nextbugrepro
Detail
I create a very simple react component.
const My = () => (<div>ABC</div>);
export default My;
It is in a standalone library project(https://github.com/jim-king-2000/react-module).
Now I use the component in another project.
// index.js
import { My } from 'react-module';
// package.json
"dependencies": {
...
"react-module": "git+https://github.com/jim-king-2000/react-module.git"
}
Then, node.js complains:
error in ./node_modules/react-module/components/My.js
Module parse failed: Unexpected token (1:18)
You may need an appropriate loader to handle this file type.
const My = () => (<div>ABC</div>);
export default My;
./node_modules/react-module/index.js 1:0-32 1:0-32
@ ./pages/index.js
@ multi ./pages/index.js
Question
How to build a ES6 react npm library?
node.js reactjs npm ecmascript-6
add a comment |
up vote
0
down vote
favorite
Repro
https://github.com/jim-king-2000/nextbugrepro
Detail
I create a very simple react component.
const My = () => (<div>ABC</div>);
export default My;
It is in a standalone library project(https://github.com/jim-king-2000/react-module).
Now I use the component in another project.
// index.js
import { My } from 'react-module';
// package.json
"dependencies": {
...
"react-module": "git+https://github.com/jim-king-2000/react-module.git"
}
Then, node.js complains:
error in ./node_modules/react-module/components/My.js
Module parse failed: Unexpected token (1:18)
You may need an appropriate loader to handle this file type.
const My = () => (<div>ABC</div>);
export default My;
./node_modules/react-module/index.js 1:0-32 1:0-32
@ ./pages/index.js
@ multi ./pages/index.js
Question
How to build a ES6 react npm library?
node.js reactjs npm ecmascript-6
This is a Webpack message. Where is the Webpack config?
– madflow
Nov 21 at 11:42
I use next.js, which uses webpack implicitly.
– Jim Jin
Nov 21 at 12:04
remove the curly braces from the import statement
– Nipek
Nov 21 at 13:12
I didn't use My.js directly. There is an index.js which reexports "My" like this "export * from './components/My';". So, the curly braces are OK. You could check the repro out to take a look.
– Jim Jin
Nov 21 at 13:15
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Repro
https://github.com/jim-king-2000/nextbugrepro
Detail
I create a very simple react component.
const My = () => (<div>ABC</div>);
export default My;
It is in a standalone library project(https://github.com/jim-king-2000/react-module).
Now I use the component in another project.
// index.js
import { My } from 'react-module';
// package.json
"dependencies": {
...
"react-module": "git+https://github.com/jim-king-2000/react-module.git"
}
Then, node.js complains:
error in ./node_modules/react-module/components/My.js
Module parse failed: Unexpected token (1:18)
You may need an appropriate loader to handle this file type.
const My = () => (<div>ABC</div>);
export default My;
./node_modules/react-module/index.js 1:0-32 1:0-32
@ ./pages/index.js
@ multi ./pages/index.js
Question
How to build a ES6 react npm library?
node.js reactjs npm ecmascript-6
Repro
https://github.com/jim-king-2000/nextbugrepro
Detail
I create a very simple react component.
const My = () => (<div>ABC</div>);
export default My;
It is in a standalone library project(https://github.com/jim-king-2000/react-module).
Now I use the component in another project.
// index.js
import { My } from 'react-module';
// package.json
"dependencies": {
...
"react-module": "git+https://github.com/jim-king-2000/react-module.git"
}
Then, node.js complains:
error in ./node_modules/react-module/components/My.js
Module parse failed: Unexpected token (1:18)
You may need an appropriate loader to handle this file type.
const My = () => (<div>ABC</div>);
export default My;
./node_modules/react-module/index.js 1:0-32 1:0-32
@ ./pages/index.js
@ multi ./pages/index.js
Question
How to build a ES6 react npm library?
node.js reactjs npm ecmascript-6
node.js reactjs npm ecmascript-6
edited Nov 21 at 13:17
asked Nov 21 at 11:32
Jim Jin
438
438
This is a Webpack message. Where is the Webpack config?
– madflow
Nov 21 at 11:42
I use next.js, which uses webpack implicitly.
– Jim Jin
Nov 21 at 12:04
remove the curly braces from the import statement
– Nipek
Nov 21 at 13:12
I didn't use My.js directly. There is an index.js which reexports "My" like this "export * from './components/My';". So, the curly braces are OK. You could check the repro out to take a look.
– Jim Jin
Nov 21 at 13:15
add a comment |
This is a Webpack message. Where is the Webpack config?
– madflow
Nov 21 at 11:42
I use next.js, which uses webpack implicitly.
– Jim Jin
Nov 21 at 12:04
remove the curly braces from the import statement
– Nipek
Nov 21 at 13:12
I didn't use My.js directly. There is an index.js which reexports "My" like this "export * from './components/My';". So, the curly braces are OK. You could check the repro out to take a look.
– Jim Jin
Nov 21 at 13:15
This is a Webpack message. Where is the Webpack config?
– madflow
Nov 21 at 11:42
This is a Webpack message. Where is the Webpack config?
– madflow
Nov 21 at 11:42
I use next.js, which uses webpack implicitly.
– Jim Jin
Nov 21 at 12:04
I use next.js, which uses webpack implicitly.
– Jim Jin
Nov 21 at 12:04
remove the curly braces from the import statement
– Nipek
Nov 21 at 13:12
remove the curly braces from the import statement
– Nipek
Nov 21 at 13:12
I didn't use My.js directly. There is an index.js which reexports "My" like this "export * from './components/My';". So, the curly braces are OK. You could check the repro out to take a look.
– Jim Jin
Nov 21 at 13:15
I didn't use My.js directly. There is an index.js which reexports "My" like this "export * from './components/My';". So, the curly braces are OK. You could check the repro out to take a look.
– Jim Jin
Nov 21 at 13:15
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
You need to setup babel compile, in order to compile jsx, which seems to be missing in your package.json
add a comment |
up vote
0
down vote
After the investigation for several hours, I find that the library has to be transpiled to ES5. I hope we could use ES6 npm modules in the future.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You need to setup babel compile, in order to compile jsx, which seems to be missing in your package.json
add a comment |
up vote
1
down vote
accepted
You need to setup babel compile, in order to compile jsx, which seems to be missing in your package.json
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You need to setup babel compile, in order to compile jsx, which seems to be missing in your package.json
You need to setup babel compile, in order to compile jsx, which seems to be missing in your package.json
answered Nov 21 at 11:49
Rohit Garg
565
565
add a comment |
add a comment |
up vote
0
down vote
After the investigation for several hours, I find that the library has to be transpiled to ES5. I hope we could use ES6 npm modules in the future.
add a comment |
up vote
0
down vote
After the investigation for several hours, I find that the library has to be transpiled to ES5. I hope we could use ES6 npm modules in the future.
add a comment |
up vote
0
down vote
up vote
0
down vote
After the investigation for several hours, I find that the library has to be transpiled to ES5. I hope we could use ES6 npm modules in the future.
After the investigation for several hours, I find that the library has to be transpiled to ES5. I hope we could use ES6 npm modules in the future.
answered Nov 21 at 15:48
Jim Jin
438
438
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411180%2fcant-import-es6-react-module%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This is a Webpack message. Where is the Webpack config?
– madflow
Nov 21 at 11:42
I use next.js, which uses webpack implicitly.
– Jim Jin
Nov 21 at 12:04
remove the curly braces from the import statement
– Nipek
Nov 21 at 13:12
I didn't use My.js directly. There is an index.js which reexports "My" like this "export * from './components/My';". So, the curly braces are OK. You could check the repro out to take a look.
– Jim Jin
Nov 21 at 13:15