"Could not load F:\tinybear\tinybearLab\rollup\libs/m1" in windows

[ideayuye]

config:
export default { entry: 'main.js', dest: 'dist/bundle.js', format: 'umd', plugins: [ alias({ libs: path.resolve(__dirname, './libs') }), uglify() ], };

import code:
import hello from "libs/m1" import hi from "libs/m2"

run :"rollup -c config.js -m inline"

Then, will expose an error:
Could not load F:\tinybear\tinybearLab\rollup\libs/m1 (imported by F:\tinybear\tinybearLab\roll up\main.js): ENOENT: no such file or directory, open 'F:\tinybear\tinybearLab\rollup\libs\m1'

But modify import code like this:
import hello from "libs/m1.js" import hi from "libs/m2.js"

run the build command will be ok.

[ideayuye]

In windows the path will be:
F:\tinybear\tinybearLab\rollup\libs/m1

But the function can't support the path:
const isFilePath = id => /^\.?\//.test(id);

So ,I modify the function to:
const isFilePath = id => /(^\.?\/)|(^[a-zA-Z]\:(\\|\/))/.test(id);

[HenriMorlaye]

Your change worked for me too on Windows 10. Thanks. Maybe this should be in a next version of this library ?

[frostney]

That's great @ideayuye @HenriMorlaye, thank you! I actually have a Win 10 machine right now for testing, let me see what I could do

[HenriMorlaye]

I was trying to build Vue.js on Windows which depends on this library. It didn't work, just changing in rollup-plugin-alias
const isFilePath = id => /^\.?\//.test(id);
to
const isFilePath = id => /(^\.?\/)|(^[a-zA-Z]\:(\\|\/))/.test(id);
made it possible to compile Vue.js for me. No idea if it creates a problem somewhere else though.

[Rich-Harris]

Hi, this repo has been adopted by the main rollup org — we've just published 1.3.0 which includes a fix for #3 which seems like it might be related to this. If you get a chance, could you check to see if this issue is fixed please? Thanks

[ideayuye]

@Rich-Harris I test the 1.3.0.Unfortunately，it still catch the error.

[Error: Could not load F:\tinybear\tinybearLab\rollup\libs/m1 (imported by F:\tinybear\tinybearLab\rollup\main.js): ENOENT: no such file or directory, open 'F:
\tinybear\tinybearLab\rollup\libs\m1']

Test code like this.
"dependencies": { "rollup": "^0.41.6", "rollup-plugin-alias": "^1.3.0", "rollup-plugin-uglify": "^1.0.1" }
build.js:

var rollup = require('rollup');
 var alias = require('rollup-plugin-alias');
 var path = require('path');
rollup.rollup({
    entry: 'main.js',
    plugins: [
        alias({
            libs: path.resolve(__dirname, './libs')
        })
    ]
}).then(function(bundle){
    bundle.write({
        format:'umd',
        dest: 'dist/bundle_api.js'
    });
    console.log('it build ok')
},function(error){
    console.log(error);
});

main.js:

import hello from "libs/m1"
import hi from "libs/m2"

hello();
hi();

libs/m1.js:

export default function hello(){
    console.log('it is m1');
}

libs/m2.js:

import hello from "./m1.js"
hello();

export default function hi(){
    console.log('hi');
}

[vjoao]

I have been able to compile Vue on Windows 10 after modifying the plugin from path.posix.resolve to path.resolve.

[mhhegazy]

@ideayuye @frostney @Rich-Harris please review PR #22 and tell if it solve this issue.

[ICELI]

Come out, my master···

[frostney]

I don't think it's as easy as just merging in #22. There are #20, #21 and #22 which all seem to fix the same issue and I'm not sure I figured out the scope of it yet. Are those different implementations, do all of them need to be merged in or something else entirely?

I'm also wondering if there's some way we could check Vue and React builds on Windows in direct relation with this plugin.

@ICELI Don't get me wrong, I do understand the frustration. I don't think airing the frustration is a constructive way to resolve the issue though.