Vasil Rangelov

Well, I'll use one of my own libraries as an example: https://github.com/pear2/Net_RouterOS In addition to normal distribution methods (PEAR, Composer, a zip and tgz archives), it is also distributed as...

> Well, if you need to require it and it's not inside the workspace, it would need #379 first. Completely acceptable caveat IMHO. > Otherwise I assume it is nothing...

> Anything you extract into a temporary folder would not be available to the client, But it doesn't need to be, does it? I mean, I'm not familiar with LSP,...

Ah. I see. That doesn't sound like a typical case to me, but I guess it's possible, so it's fair to support it. So yeah, the client would need to...

I don't have complete numbers, and I can only speak for my libraries, but... any library that I have published a PHAR release of is used more often in that...

@staabm Right... That's the most common use. Like I said, seasoned developers tend to use Composer for libraries, since it allows them to manage incompatibilities between different libraries easier, and...

This seems like an oversight on nest-cli's side. I've made nestjs/nest-cli#538 to make it use use node's internal resolution, same as tsc when it loads plugins, and as the average...

IMHO, these sorts of "wildcard" magic methods and properties are best documented at `__get` and `__call`'s long descriptions. If you actually have a specific set of allowed methods/properties, you can...

> Since the phpDoc is the starting point for IDEs to follow, I thought implementing it in the official supported syntax would be easier to implement in IDEs. That's true,...

My critisisms earlier apply to this example as well. How do you address those?