Watch the buildinfo file

[EduardoLopes]

Hello!

I'm developing a component library within a monorepo. This monorepo also contains the documentation application for the library.

When I make a change to the library, a new buildinfo file is generated.

The problem is that this change isn't detected by:

• The documentation app (which is inside the monorepo).
• My main application (which is outside the monorepo and consuming the library, likely via npm link).

For both applications, I have to stop and restart the dev server to see the new CSS generated from the updated buildinfo file.

Is there any way to make Panda watch for changes to this buildinfo file from a local library so I don't need to restart the server?

If this isn't supported yet, I'm willing to look into the codebase and help contribute this feature if it's aligned with the project's plans.

Thanks!

edit: the application updates with the new generated classes. but the classes doesn't have effect because the css was not generated.

[segunadebayo]

Did you try adding the buildinfo file to the includes option in the panda.config.ts?

We're open to ideas that help improve the monorepo DX

[EduardoLopes]

Yes, I tried, but it didn't work at the time.

I identified a problem in my setup: the buildinfo file is located within a package. In the main application, I was using the component library and getting the buildinfo file from the node_modules folder. However, node_modules was being excluded from the in panda config, which I believe was the cause of the issue i had.

Now, in the documentation app, I've pointed the path directly to the module, outside of node_modules, and it works correctly.

In the main application, outside the monorepo, I'm observing some peculiar results with hot-reloading, but they resemble the expected behavior during a hard reload. This is an improvement over stopping and restarting the server.

I think it's a good idea to create an example monorepo for working with this setup.
I will conduct further tests and return with more detailed information.

[EduardoLopes]

I've done considerable digging but haven't fully pinpointed the exact cause. However, my strongest hypothesis is that the exclude pattern is taking precedence over the include pattern.

{
  "include": [
    "./src/**/*.{ts,tsx,svelte}",
    "./node_modules/@pindoba/panda-buildinfo/dist/**/*.json" // ← Explicitly included the buildinfo file!
  ],
  "exclude": [
    "**/node_modules/**" // ← This appears to OVERRIDE the include above! but even if i remove this completely, the problem still happend
  ]
}

Additionally, @pindoba/panda-buildinfo is a symlink, as I'm currently doing local development using pnpm link. This might introduce another layer of complexity.

The end-user will add the buildinfo file to their include list and won't update the library locally. Therefore, as the configuration stands, it works for them. Since I've found a workaround for my specific usage by directly including the file via the path ../pindoba/packages/panda-buildinfo/dist/panda.buildinfo.json (which is outside node_modules), I will stop investigating this issue further for now.