4 ms·
It generates a map file when you run `composer install` and many of the several other commands. Yours is not really a critique of composer, since it's not a da
by jtreminio 8y ago
It generates a map file when you run `composer install` and many of the several other commands.
Yours is not really a critique of composer, since it's not a daemon or a continuously run script. You run it once and done.
- workinthehead 8y agoNo, it is though, because other package managers are not daemons and they don't have this problem.
- sieabahlpark 8y agoComposer is optimized for how php executes which is once per request. If you want to compute namespaces per request that's your choice.
- workinthehead 8y agoWell, that's not really true either since most production PHP deployments use FastCGI. The problem isn't namespaces, either, since this applies to packages that don't use namespaces. (But what kind of a language requires you to "compute namespaces" outside of runtime, anyway?) So I'm forced to conclude you don't know what you're talking about. Probably one of those butthurt PHP partisans who can't handle criticism. checks profile Ah, indeed.
- tylerjwilk00 8y agoIf you wish to daemonize it have a file change listener run it when it observes file system changes in the appropriate directory. If that is too much work a quick hack would be: watch -n 10 composer dumpautoloaf --no-scripts & Full disclosure: I did not verify this command would work well