QuickStart not installing all the dependencies

Technical Questions
, ,
1

I am trying to install my app with Quick start for on a next-js project but apparently
the BuilderDevTools is missing in the dependencies :

I get this error when running npm run dev :

⨯ Unable to acquire lock at C:\Users\Admin\OneDrive\Documents\EcommFox_Digital\Ecommfox\Porfolio\builder-app\.next\dev\lock, is another instance of next dev running?
  Suggestion: If you intended to restart next dev, terminate the other process, and then try again.

I ran the Quickstart command as shown in the documentation
Builder was intalled correctly but had to run npm install once more because of missing dependecies :

made sure all the version are up to date : node , next-js , react

Any one else get this issue ?

2

When i modify my next.config.mjs file to :

/** @type {import('next').NextConfig} */
const nextConfig = {
  /* config options here */
  reactCompiler: true,
};

export default nextConfig;

I don’t have this issue but ofc Builder is not render on my page
( i chose Javascript in the installation process – not TS )

3

Hello @Ecommfox,

Could you please confirm which version of Next.js you are currently using?

We attempted to reproduce the issue on our end using "next": "16.1.6" but were unable to replicate the same error. That said, we have seen some issues when using DevTools with Next.js Turbopack, so we want to confirm whether that might be a factor in your setup.

4

I confirm Next.js v16.1.6 installed , I was aware turbopack causes issue so i forced --webpack in the package.json

Edit :
Apparently on changing the script in package.json to :

 "scripts": {
    "dev": "next dev --webpack",
    "build": "next build --webpack",
    "start": "next start",
    "lint": "eslint"
  },

next turbopack , npm install should run normally but during the build I enconter the errror with isolated-vm

For reference it’s apparently the same issue as in this thread

But I am not using an Apple machine , i’m on a windows system

5

@manish-sharma I found there were several issue in my setup :
Node.js was not up to date , so to avoid having the isolated-vm issue, making sure to have the latest version of node.js is the best solution .

Other fix : import { BuilderDevTools } from '@builder.io/dev-tools/next'; did not work after running a new build, builder.io was reinstalled with all the dependencies but I had to import NextBuilderDevTools in my next.js config .

1 Like