Alias plugin is not compatible with rollup-plugin-alias

[thgh]

• Rollup Plugin Name: alias
• Rollup Plugin Version: 2.2.0
• Rollup Version: latest
• Operating System (or Browser): unix
• Node Version: 12

How Do We Reproduce?

Add alias({ src: __dirname + '/src' }) to rollup plugins

Expected Behavior

import 'src/util.js' works

Actual Behavior

internal/modules/cjs/loader.js:775
    throw err;
    ^

Error: Cannot find module 'src/util.js'

The API change in plugin-alias@2 breaks the old behaviour for no apparent reason. It's perfectly possible to add a special entries option. It's sad that a project with 20k+ downloads/week can just break dependency upgrades because one developer feels like it.
Breaking PR: rollup/rollup-plugin-alias#53
Previous issue: rollup/rollup-plugin-alias#58
Still incompatible PR: rollup/rollup-plugin-alias#61

(sorry for repeating this issue)

[shellscape]

@thgh The tone of this one could be a little more friendly. The change was debated and discussed by @thiscantbeserious, @Andarist, and @lukastaegert - hardly one user. I'd argue it was up for a reasonable amount of time for discussion as well. From what I understand, the API changed, but the functionality remains.

[thiscantbeserious]

Edited out unrelevant non-constructive comment from my side.

---

Any reason why you don't stick with V1 if you don't need the functionality that V2 brings?

[Andarist]

The reason for a change was simple - we believe that this is a better API than what was present in v1. It was hardly for "no apparent reason" - v2 was intentionally published as a major version and thus breaking changes are expected.

[shellscape]

@thgh has done a lot for Rollup over the years, so I highly doubt the concerns are conveyed with ill intent. I'd ask everyone commenting take that into consideration. I didn't tag everyone with the intent to cause a pile-on, rather to further discuss the changes that were made.

I'd be interested to know if there's middle ground here.

[thgh]

First of all, sorry for the tone of the issue. I think it's fantastic that you all take the initiative to maintain many plugins. Also, I'm definitely not trying to point fingers (even though I see now that it looked that way). It's more that I'm concerned about the stability of the Rollup plugin ecosystem.

Another concern is that tons of developers have struggled to configure webpack. Requiring them to learn another plugin configuration brings mental overhead. The effort to support both syntaxes in code is trivial, so I think the tradeoff leans in that direction.

I hope the PR brings us closer to middle ground ;-)

Note: I'm currently sticking to v1, but it's marked as deprecated (which triggered me to post this issue).