Support for default folder structure generated by `firebase init` about isolate-package HOT 2 CLOSED

The Firebase team did not have monorepos in mind when they decided on that structure, and I think it is not a pattern I want to encourage.

I would rather spend some time to figure out what is up with the reloading of the emulator, and add a how-to section to the readme. If the emulator relies on this structure for reloading then I would consider that a bug for Firebase to solve.

I don't think the init folder structure is desirable today in the context of a monorepo, so I am reluctant to invest time in this myself.

However, I would accept a PR from someone, as long as it doesn't complicate the code too much.

from isolate-package.

I had a look at the firebase init output, and my conclusion is that it is just not designed with monorepos in mind, like I already suspected. It does contain multiple package files, but doesn't utilize workspaces at all.

Nested packages in monorepos is just not a thing AFAIK. I know for certain that Turborepo and Yarn do not support it.

If the Firebase team wants to make it easy for developer to start working with a monorepo setup, they should update their init command to facilitate it. I have no desire to change isolate to support their current structure, so I'm closing this issue.

It should be easy enough to move some files around. It's a bit of extra work, but I think it's worth learning how monorepos are structured anyway.

from isolate-package.