Full documentation of `prismic sm` command?

Slice Machine Developer Workflow
#1

While I really appreciate the idea of the Slice Machine generator, in some use cases it just doesn't work. I'll give my specific use case: I'm using NX (nx.dev) to manage a monorepo and create a Next.js site inside it. Because of the way NX manages the dependencies and the monorepo, the assumed location of files (like the project root, package.json, etc.) is going to be incorrect.

So, what I'd love to see is a step by step document (maybe here? https://prismic.io/docs/technologies/running-the-prismic-slice-machine-command-nextjs) of everything prismic sm does so I can effectively replicate it inside my repo.

I'll see if I can help with that, but being new to Prismic in general, especially to SliceMachine, I may not get things as "correct" as others with experience might. (And if this already exists, please feel free to correct me.

#3

Hi Jason,

Welcome to the community!

Are you maybe describing something like this listing the options for the command? There's some options here for specifying different project trees.

Or something more in-depth that describes what the CLI actually does when it uses these commands?

#4

@Phil First, thanks for the quick reply. This is hugely helpful, but unfortunately not quite what I need. What I'm looking for is a delineation of what files are created and modified as a result of the prismic sm --setup command so I can replicate that automated step manually.

I "kinda" cheated and created one outside of my NX repo and just updated the files as I checked the diffs, so I have some kind of idea of what it does, but I may have missed something.

I'll admit, on principle, it's just that I really dislike when libraries do automated stuff without also providing documentation of how to accomplish the same thing manually. It's the black box nature of it, I guess.

I'll see if I can't build something that could be used in the documentation.

#5

OK, I understand better. I can see that we just listed the files that were updated, rather than what was updated in each file.

I'll add it to our backlog to better list EXACTLY what this command does in detail. I totally respect that you want to know what's going on.

#6