Why is the API of Parcel 2 more restrictive compared to V1?

[AndyOGo]

First, Parcel 2 works great and is super easy when used as a CLI tool.

Though as soon as I want to use it programmatically, I'm faced with certain restrictions not present in Parcel V1.

• accessing the e.g. bundler's options is prohibited because almost all members are private in Parcel V2
  

  parcel/packages/core/core/src/Parcel.js

  Lines 80 to 82 in 47379bf

  	constructor(options: InitialParcelOptions) {
  	this.#initialOptions = options;
  	}

  
  Parcel V1 allowed to access them, like:
  

  parcel/packages/core/parcel-bundler/src/Server.js

  Lines 35 to 36 in e11f085

  	function middleware(bundler) {
  	const serve = serveStatic(bundler.options.outDir, {

• adding or testing local plugins programmatically need a separate package for each plugin One-off/local plugins #4321
• Extending / inheriting from existing plugins in Parcel 2 Extend / inherit from existing plugins in Parcel 2 #7680
• using Parcel as middleware has been removed Express Middleware in Parcel 2? #4612

IMHO these restrictive changes are daunting and frustrating to work with.
Could you please explain why the API is designed that way? What are the benefits?

[mischnic]

using Parcel as middleware has been removed

This is because the server is just a regular plugin, so there's no special way it's exposed in the core JS api.

adding or testing local plugins programmatically need a separate package for each plugin

The original idea was described here: #4321 (comment)

accessing the e.g. bundler's options is prohibited because almost all members are private in Parcel V2

Maybe we could expose that similar to how options is passed to plugins...

[AndyOGo]

Thank you for your reply @mischnic

This is because the server is just a regular plugin, so there's no special way it's exposed in the core JS api.

I understand.
It would be great, if I could interact to some extend also from the outside via the API with the bundler.
Or at least have the meta data available as read-only members.

The original idea was described here: #4321 (comment)

I see the community viewpoint behind it, though I think it puts too much control and is more a stop than a go.

Maybe we could expose that similar to how options is passed to plugins...

It would be really nice for my case, so that I can pass a bundler object around, and other tools can read e.g. the outDir options or whatever they need.