-
Notifications
You must be signed in to change notification settings - Fork 126
Broken in [email protected] #63
Comments
I'm on windows, fwiw. Looking to see why tests aren't failing in node6 atm. |
Ok, I see why this is failing for me but not in the tests. My repo invokes rollup like this: The first time the The tests don't run into this because their But that seems really unexpected and wrong. I think the check in /src/index.js#L67 should be changed to: if ( importee[0] !== '.' || !importer ) return; // not our problem Thoughts? All the tests still pass w/ that change, because it's only true for the entry module which should always be an ES Module (I assume). |
See rollup#63 for an explanation of why.
Same issue with Mac OS X and Node 6. |
Fixed in 3.1.0, thanks for the PR @tivac |
I'm getting this on node 4.4.5:
My module.exports = {
entry : './src/index.js',
dest : './build/index.js',
format : 'iife',
sourceMap : true,
plugins : [
require( 'rollup-plugin-buble' )( {
transforms : {
dangerousForOf : true,
dangerousTaggedTemplateString : true
}
} ),
require( 'rollup-plugin-commonjs' )( {
include : './node_modules/**'
} ),
require( 'rollup-plugin-node-resolve' )( {
jsnext : true,
main : true
} )
]
} My {
"rollup": "0.33.1",
"rollup-plugin-buble": "0.12.1",
"rollup-plugin-commonjs": "3.1.0",
"rollup-plugin-node-resolve": "1.7.1",
"rollup-watch": "2.4.0"
} EDIT: locked down the version numbers, removed node_modules, cache cleaned, reinstalled, reproduce Any ideas? |
That error is coming from the rollup-plugin-node-resolve module. It'll work once rollup/rollup-plugin-node-resolve#45 is merged, but until then you can work around it by removing './' from the entry filename. |
Thanks @lammas — I spotted the error just as you posted. Confirmed fixed! |
rollup-plugin-commonjs
is broken in[email protected]
due to thepath
module throwing if any of its input is not a string.A small repro can be found here: https://gist.github.com/tivac/f4f8b4086fb8bc0c9d1cd166f1a2b396
/src/index.js#L69 is causing the issue, I haven't dug in deeper yet.
The text was updated successfully, but these errors were encountered: