Monday, June 3, 2024
 Popular · Latest · Hot · Upcoming
53
rated 0 times [  60] [ 7]  / answers: 1 / hits: 19631  / 9 Years ago, thu, may 21, 2015, 12:00:00

I'm working with Babelify and Browserify. Also, I'm using ES6 style module features by node module system.



I would like to put all my own modules into node_modules/libs.



For instance:



test.js in node_modules/libs



export default () => {
console.log('Hello');
};


main.js (will be compiled to bundle.js)



import test from 'libs/test';

test();


After that, I have compiled the above codes to bundle.js with this command:



browserify -t babelify main.js -o bundle.js


But unfortunately, I have got some error:



export default () => {
^

ParseError: 'import' and 'export' may appear only with 'sourceType: module'


Directory structure:



[test]
`-- node_modules
│ `-- libs
│ `-- test.js
`-- main.js


But, when own modules not in node_modules like this:



[test]
`-- libs
│ `-- test.js
`-- main.js


Then, it works fine. How can I use the ES6 style modules with babelify in node_modules?


More From » node.js

 Answers
6

That is how Browserify transforms work, transforms only have an effect directly in the module that is being referenced.



If you want a module in node_modules to have a transform, you'd need to add a package.json to that module and add babelify as a transform for that module too. e.g.



browserify: {
transform: [
babelify
]
},


inside your package.json plus babelify as a dependency will tell browserify to run the babelify transform on any file inside that module.



Having libs be a folder in node_modules is however probably a bad idea. Generally that folder would have true standalone modules in it. I'd generally say that if the folder can't be taken and reused elsewhere, then it shouldn't be in node_modules.



Update



For Babel v6, which was recently released, you will also need to specify which transformations you would like to perform on your code. For that, I would recommend creating a .babelrc file in your root directory to configure Babel.



{
presets: [es2015]
}


and



npm install --save-dev babel-preset-es2015

[#66506] Tuesday, May 19, 2015, 9 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
zainsagez

Total Points: 555
Total Questions: 99
Total Answers: 96

Location: Honduras
Member since Sat, Jul 24, 2021
3 Years ago
zainsagez questions
;