Initialising slicemachine results in error finding @slicemachine/adapter-universal

Developing with Prismic
,
1

I've tried to initialise slice machine on a new react repo (a remix app). It tries to install v2.0.0 with the new slicemachine.config.json.

{
  "apiEndpoint": "https://redacted.prismic.io/api/v2",
  "repositoryName": "redacted",
  "adapter": "@slicemachine/adapter-universal",
  "libraries": ["./slices"]
}

In my case this then fails because @slicemachine/adapter-universal is not published to the npm registry.

Is there a known workaround to this?

1 Like
2

Hey! I had the same problem. I think it is some mistake
I have replaced "adapter": "@slicemachine/adapter-universal" with "adapter": "@slicemachine/adapter-nuxt", and seems like it works fine.

{
  "apiEndpoint": "https://efendiler.prismic.io/api/v2",
  "repositoryName": "efendiler",
  "adapter": "@slicemachine/adapter-nuxt",
  "libraries": ["./slices", "vue-essential-slices"],
  "localSliceSimulatorURL": "http://localhost:3000/slice-simulator"
}

I hope team will fix it

5

Some info from the devX team:

Slice Machine only supports Next.js and Nuxt at this time. We are currently exploring which frameworks we will support in the future (including the possibility for a “universal” adapter that supports any framework). Until then, Slice Machine will not work in a Remix application. It's possible to manually use the Next.js adapter (@slicemachine/adapter-next ), but it is not something we recommend or support.---

6

Hi @Pau, thanks for the info.

Slice machine works fine, albeit in a more limited way with remix and I'm OK with that.

The problem I wanted to highlight was that the latest config version references a package that doesn't exist on NPM. Not only that, the error doesn't suggest a way for the developer to fix it which wastes a lot of time hunting for fixes.

Thanks,

Ben

3 Likes