entry-point [!] Error: ENOENT: no such file or directory

[ricksunxxx]

• Rollup Plugin Name: @rollup/plugin-multi-entry
• Rollup Plugin Version: 3.0.0
• Rollup Version: 1.27.10
• Operating System (or Browser): windows
• Node Version: 10.15.3

is anyone who could tell me how to fix it ?

[shellscape]

Hey thanks for opening an issue. Unfortunately this isn't the right place to ask for support. Citing the issue templates:

Hey there! If you need help or tech support then this is not the place to
ask. Please head to the Rollup Gitter
instead or post a question to https://stackoverflow.com/questions/tagged/rollupjs.

👉🏽 Need help or tech support? Please don't open an issue!
Head to https://gitter.im/rollup/rollup or https://stackoverflow.com/questions/tagged/rollupjs

Apologies, but we don't have the bandwidth to service both support requests and technical issues for Rollup. Please try one of the avenues mentioned above (and in the issue templates).

[xinaesthete]

I believe this is indeed a bug. Taking a working configuration and invoking this plugin causes the above error to appear, even before any configuration that would cause it to become effective is introduced.

My config:

import ts from '@rollup/plugin-typescript';
import resolve from '@rollup/plugin-node-resolve';
import multi from '@rollup/plugin-multi-entry';

export default {
    input: ['TS/mod/test.ts'],
    //input: 'TS/mod/**/*.ts', //if the plugin was working, I'd use something like this.
    plugins: [
        //multi(), //uncommenting this line will cause an error
        ts(), resolve()
    ],
    output: {
        dir: 'dist',
        //entryFileNames: '[name]--r.js',
        format: 'esm',
        sourcemap: true
    }
}

I don't think interactions with other plugins are to blame, but I haven't tried a more minimalistic configuration as yet. I am on a slightly more recent rollup (1.29.0) and node (v12.13.1).

[shellscape]

@xinaesthete if you can put together a minimal reproduction, we'll reopen this as a bug to triage. Good repros are:

1. Using the REPL.it plugin reproduction template at https://repl.it/@rollup/rollup-plugin-repro
2. Provide a minimal repository link (Read https://git.io/fNzHA for instructions).
   These may take more time to triage than the other options.
3. Using the REPL at https://rollupjs.org/repl/, or

[xinaesthete]

@shellscape ok, but literally all that seems required to repro is to install and invoke the plugin... (and I should get to bed now).

Thanks for the quick response.

[xinaesthete]

hmm, first attempt at minimal repro in repl.it did not repro, will keep you posted.

[shellscape]

That's why we ask for them 😄

I would say next step is to create a new repo to try and reproduce the problem. If that doesn't show a reproduction, then we can try taking a look at a repo that does. A lot of the time these types of things boil down to a specific environment issue. Sometimes we can spot what it is, other times it takes a ground-up rebuild of a repo to identify the culprit (typically a last resort).

[xinaesthete]

It appears to be a Windows issue. I've now tried with my mac this morning and the same project is ok there. I'll set up a quick minimal repo and try it in a couple of different environments now.

[xinaesthete]

I only just noticed, it does behave differently on macos, but still doesn't work properly. On mac, no error is reported, but a file is written with a name like '_rollup:plugin-multi-entry:entry-point.js'. Presumably the difference is in how the different platforms treat colon in filenames.