Slice Machine and multiple devs solutions

Developing with Prismic
1

Dear Prismic team,

One thing my dev team has really struggled with in Slice Machine is having multiple developers working at the same time.

Whenever several slice changes need to happen in parallel, things can get pretty chaotic. It ends up requiring a lot of coordination, timing, communication, and merge conflict resolution because everything eventually gets folded into the same prismicio-types.d.ts file.

One thing I think works really well is how the customtypes folder is structured. If I make changes to one Custom Type and another developer is working on a completely different one, we generally don't run into any issues because they're separate files.

Has the team ever considered doing something similar with prismicio-types.d.ts? Maybe having it act as the source of truth, but generating types in a more modular way so developers are working in separate files instead of constantly touching one large file.

It feels like if the type system worked more like the Custom Types structure, multiple developers could work throughout the Slice Machine ecosystem without stepping on each other's toes, as long as they aren't editing the same slice. It would make collaboration a lot smoother for larger teams.

Curious if this is something that's been discussed and if there is a plan to resolve this issue in the near future.

2

Hey, thanks a lot for the detailed messages and the suggestion. It's a good observation.

To be upfront: we're deprecating Slice Machine, so it won't get new work in this area, we're focusing on Type Builder + CLI going forward.

We're currently writing the documentation for migrating from Slice Machine to Type Builder, and we'll share it here once it's ready.

The migration won't make this conflict disappear entirely, but it makes it much simpler: prismicio-types.d.ts is a generated file, so you treat a conflict on it like one on package-lock.json / yarn.lock, don't merge by hand, just regenerate it with a single command (npx prismic gen types), even mid-merge.

Thanks again, we'll be back on this once the migration guide is out.