DevLink Issues and Solutions

So far, I’m in love with DevLink.

I had just finished designing my UI in Webflow and was preparing to move it over to a Next.JS project on Vercel when I got the Beta notification… Fantastic timing.

Two bugs I’ve found so far:

The way DevLinkProvider gets imported by default fails, but when I added the /devlinkContext path, it solved it.

import { DevLinkProvider } from “@/devlink”; (default)
import { DevLinkProvider } from “@/devlink/devlinkContext”; (working)

However, when I redeploy, I then get a list of import issues:

Attempted import error: ‘createContext’ is not exported from ‘react’ (imported as ‘React’).
Attempted import error: ‘useRef’ is not exported from ‘react’ (imported as ‘React’).
Attempted import error: ‘useEffect’ is not exported from ‘react’ (imported as ‘React’).
Attempted import error: ‘useLayoutEffect’ is not exported from ‘react’ (imported as ‘React’).

Since React Hooks and Context only work on Client Components, I fixed this by adding the “use client” directive at the top of every devlink file that imports * from react

The way DevLinkProvider gets imported by default fails

@Perkail mind clarifying this? what errors do you get when using the default import from “@/devlink”?

How did you add the use client directive?