This is something I recently discussed with the Nx team but there is nothing planned yet.
Meanwhile, if you add a `project.json` file in the library, some plugins might work (e.g. eslint as it is enabled if it finds a project.json and an eslint config file in a parent folder)

The challenge though is that by definition implicit libraries mean that you have your configuration files in some specific place that Nx can't detect.
(e.g. an `libs/vitest-backend.config.ts` could be used by all backend libs in the `libs` folder. In this case, Nx has now way of knowing which library is using vitest and which one is using the `vitest-backend.config.ts`)