@mui/x-data-grid contains separate package.json under components/ folder so I think that will be picked up by read-package-json

But some files under components/ are still grouped under the real npm package

{:npm-info {:package-id "/home/juho/Work/foo/bar/frontend/node_modules/@mui/x-data-grid/components@",
                             :package-name nil,
                             :version nil},
                  :output-name "module$node_modules$$mui$x_data_grid$components$containers$GridRootStyles.js",
                  ...

hmm yeah weird package.json contents confuse the system a little bit

I guess it should keep looking up for "name" if there isn't one

https://github.com/thheller/shadow-cljs/issues/1074

I did look at shadow.build.npm but as far as I understand, it is finding the closest package.json on purpose, so it doesn't seem to be trivial to change this. Perhaps there should be separate info for "real" package.json for the files that are under these nearly empty package.json files, and then build report could use that information.

yeah the name and version fields are only used for the build report. the other stuff is more important for the actual build

should still work properly though, I'll check it out

oops, fixed

ty