Error: Cannot find module '../build/output/log' on next start

[AryanJ-NYC]

Has anyone run into the following error?

2020-07-06T22:32:38.199924958Z >configurator@0.1.0 start /home/site/wwwroot
2020-07-06T22:32:38.199929958Z > next start -p $PORT
2020-07-06T22:32:38.199935458Z 
2020-07-06T22:32:38.328916861Z internal/modules/cjs/loader.js:960
2020-07-06T22:32:38.328954062Z   throw err;
2020-07-06T22:32:38.328966662Z   ^
2020-07-06T22:32:38.328970962Z 
2020-07-06T22:32:38.328974962Z Error: Cannot find module '../build/output/log'
2020-07-06T22:32:38.328979062Z Require stack:
2020-07-06T22:32:38.328982862Z - /home/site/wwwroot/node_modules/.bin/next
2020-07-06T22:32:38.328987162Z     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
2020-07-06T22:32:38.328991162Z     at Function.Module._load (internal/modules/cjs/loader.js:840:27)
2020-07-06T22:32:38.328995062Z     at Module.require (internal/modules/cjs/loader.js:1019:19)
2020-07-06T22:32:38.328998962Z     at require (internal/modules/cjs/helpers.js:77:18)
2020-07-06T22:32:38.329002862Z     at Object. (/home/site/wwwroot/node_modules/.bin/next:2:46)
2020-07-06T22:32:38.329007263Z     at Module._compile (internal/modules/cjs/loader.js:1133:30)
2020-07-06T22:32:38.329011263Z     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
2020-07-06T22:32:38.329015563Z     at Module.load (internal/modules/cjs/loader.js:977:32)
2020-07-06T22:32:38.329019563Z     at Function.Module._load (internal/modules/cjs/loader.js:877:14)
2020-07-06T22:32:38.329023363Z     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12) {
2020-07-06T22:32:38.329027363Z   code: 'MODULE_NOT_FOUND',
2020-07-06T22:32:38.329031163Z   requireStack: [ '/home/site/wwwroot/node_modules/.bin/next' ]
2020-07-06T22:32:38.329035163Z }
2020-07-06T22:32:38.343932552Z npm info lifecycle configurator@0.1.0~start: Failed to exec start script
2020-07-06T22:32:38.345497383Z npm ERR! code ELIFECYCLE
2020-07-06T22:32:38.346137195Z npm ERR! errno 1
2020-07-06T22:32:38.347402320Z npm ERR! configurator@0.1.0 start: `next start -p $PORT`
2020-07-06T22:32:38.347925430Z npm ERR! Exit status 1
2020-07-06T22:32:38.348429339Z npm ERR! 
2020-07-06T22:32:38.349004551Z npm ERR! Failed at the configurator@0.1.0 start script.
2020-07-06T22:32:38.349526261Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-07-06T22:32:38.383122513Z npm timing npm Completed in 308ms
2020-07-06T22:32:38.383874227Z 
2020-07-06T22:32:38.384504340Z npm ERR! A complete log of this run can be found in:
2020-07-06T22:32:38.385024550Z npm ERR!     /root/.npm/_logs/2020-07-06T22_32_38_351Z-debug.log

I'm trying to deploy my NextJS application to Microsoft Azure (using app Services) but am running into this odd roadblock. A quick Google search shows an extremely similar, mysterious bug: https://stackoverflow.com/questions/62378045/how-to-fix-next-js-vercel-deployment-module-not-found-error

Has anyone encountered this before?

[archywillhe]

yeah just got into this too

[walela]

@archywillhe @AryanJ-NYC You're probably accidentally committing your node_modules to your project's git repo. Try deleting it, adding a gitignore and pushing to github. Your deployment should work.

[jmcshane]

@AryanJ-NYC I'm getting this same issue on Azure. Can you share the root path environment variable?

[AryanJ-NYC]

@jmcshane ROOT_DIRECTORY=/home/site/wwwroot

[jmcshane]

@AryanJ-NYC I am so grateful for your response here. You have saved me so much time today 😀

[rapritchard]

@AryanJ-NYC Where exactly do you put that enviorment variable on azure? I'm having the same problem right now.

[melbourne2991]

Also getting this on AWS 😢

[RaulButuc]

If you are trying to deploy a NextJS production build successfully on an Azure WebApp using Azure DevOps' Pipelines, this is how I got it sorted out:

Pipeline deployment.yml:

trigger:
- master

variables:
  azureSubscription: 'confidential'
  webAppName: $(HORIZON)
  environmentName: $(HORIZON)
  vmImageName: 'ubuntu-latest'

stages:
- stage: Build
  displayName: Build Horizon
  jobs:  
  - job: Build
    displayName: Build
    pool:
      vmImage: $(vmImageName)
      
    steps:
    - task: NodeTool@0
      inputs:
        versionSpec: '10.x'
      displayName: 'Install node.js'

    - script: yarn
      displayName: 'Install dependencies'
    
    - script: yarn export
      displayName: 'Export production build'

    - task: ArchiveFiles@2
      displayName: 'Archive files'
      inputs:
        rootFolderOrFile: '$(System.DefaultWorkingDirectory)'
        includeRootFolder: false
        archiveType: zip
        archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
        replaceExistingArchive: true

    - upload: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
      artifact: drop

- stage: Deploy
  displayName: Deploy Horizon
  dependsOn: Build
  condition: succeeded()
  jobs:
  - deployment: Deploy
    displayName: Deploy
    environment: $(environmentName)
    pool: 
      vmImage: $(vmImageName)
    strategy:
      runOnce:
        deploy:
          steps:
          - task: AzureWebApp@1
            displayName: 'Azure Web App Deploy: $(HORIZON)'
            inputs:
              azureSubscription: $(azureSubscription)
              appType: webAppLinux
              appName: $(webAppName)
              runtimeStack: 'NODE|10.10'
              package: $(Pipeline.Workspace)/drop/$(Build.BuildId).zip
              startUpCommand: 'yarn start'

The scripts in my package.json:

"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "node_modules/next/dist/bin/next start -p $PORT",
    "export": "next build && next export"
  },

And my server.js (very important):

const express = require('express')
const next = require('next')

const dev = process.env.NODE_ENV !== 'production'
const port = process.env.PORT || 3000
const app = next({ dev })
const handle = app.getRequestHandler()

app.prepare()
.then(() => {
  const server = express()

  server.get('/p/:id', (req, res) => {
    const actualPage = '/post'
    const queryParams = { title: req.params.id }
    app.render(req, res, actualPage, queryParams)
  })

  server.get('*', (req, res) => {
    return handle(req, res)
  })

  server.listen(port, (err) => {
    if (err) throw err
    console.log('> Ready on http://localhost:' + port)
  })
})
.catch((ex) => {
  console.error(ex.stack)
  process.exit(1)
})

Extra .gitignore:

// .gitnignore

build/
.next/
out/
.env
.env.build
node_modules/
jspm_packages/
/.pnp
.pnp.js
dist/
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pids
*.pid
*.seed
*.pid.lock
lib-cov
coverage
.nyc_output
bower_components
.npm
*.tgz
.yarn-integrity
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local
npm-debug.log*
yarn-debug.log*
yarn-error.log*

[Riccardo-Andreatta]

Why do you need a server.js if you are not even running it?

[bviala]

The fixed start script was enough to solve the issue for me:

"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "node_modules/next/dist/bin/next start -p $PORT",
  },

My very simple pipeline:

# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml

trigger:
- dev

steps:

- script: npm ci
  displayName: Install packages

- script: npm run build
  displayName: Build

- task: ArchiveFiles@2
  displayName: Archive
  inputs:
    rootFolderOrFile: '$(System.DefaultWorkingDirectory)'
    includeRootFolder: false
    archiveType: 'zip'
    archiveFile: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'
    replaceExistingArchive: true

- task: AzureRmWebAppDeployment@4
  displayName: Deploy
  inputs:
    ConnectionType: 'AzureRM'
    azureSubscription: 'xxxxxxxxxxxxxx'
    appType: 'webAppLinux'
    WebAppName: 'xxxxxxxxxxxx'
    packageForLinux: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'
    RuntimeStack: 'NODE|18-lts'
    StartupCommand: 'npm run start'

[Gr8z]

This error occurs when your nextjs symlinks are missing. Make sure when you compress your files before deployment, you also store symlinks.

Here is a zip command that I use:

zip -r --symlinks deploy.zip . -x node_modules/\* *.git*

[cliffbdf]

I don't use React, and so I don't understand this. I am just running the app per the instructions on the OpenAI site, which say,
npm install
npm run dev

but I get the error,
Error: Cannot find module '../build/output/log'

which gets thrown at,
node_modules/.bin/next:7:35

and indeed, if I look in there, line 7 says,
var log = _interopRequireWildcard(require("../build/output/log"));

but I don't have a ../build directory. Not sure what to do. Any ideas??? Help would be appreciated!

[benvium]

FWIW I got this error when I copy-pasted a nextjs app folder (including a node_modules folder) to a new location. Fixed with rm -rf node_modules && npm i.

Presumably because the copy-paste broke the nextjs symlinks that Gr8z mentioned above

[mcuckson]

For those people finding this issue while deploying to Azure, the symlinks need adding as per @Gr8z solution but you need to keep the node_modules otherwise it won't have the packages after deployment.

From my Azure pipeline:

- script: zip -r --symlinks '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip' .

[gabrielbarceloscn]

Combination that worked for me:

Devops Build Pipeline:

- script: |
    zip -r --symlinks '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip' .
  displayName: 'ZIP com SymLinks'
  workingDirectory: 'modules/web'

packages.json

"scripts": {
.......
    "start": "node_modules/next/dist/bin/next start -p $PORT",
........
  },

[atakane]

I've been trying to find a way to solve the problem for a while now. Thank you!

[wazcov]

Just had this issue randomly appear and adding --symlinks to the zip command fix it, no idea why!

[cmvallat]

lifesaver

[dimaboychev]

Can you show where in the pipeline yml file you add the --symlink zip command? I'm confused about the whole structure. My deployment.yml file looks almost the same like @bviala posted above

[cmvallat]

I didn't have a yml file unfortunately, I just zipped and uploaded to AWS Beanstalk manually

[bandekarkunal]

Just delete the node_modules and run npm install.
This should fix the issue.

[vi4hu]

I recently got this error while building nextjs in AWS Codepipeline. Running npm rebuild in the working directory solved it for me.

Cause

As suggested by this thread the problem is with the symbolic links of npm

Solution

The solution for AWS Pipeline.

1. build your project with Codebuild (buildspec) as usual
2. Run the rebuild in Codedeploy after install script to fix the node_modules/.bin symlinks

cd /home/user/yourproject
sudo /usr/bin/npm rebuild

Pros:

1. Don't need to remove and install the modules again (was causing downtime)
2. Easy to automate for different CI/CD platforms

Cons

1. ?

[yangqiong]

where add rebuild command

[vi4hu]

where add rebuild command

You need to run the command in the project root directory(where nodemodules are present).

If you are using a pipeline tool then make sure when you run the cmd you are in project root.

# aws after install script example
cd /home/<user>/yourprojectdir
sudo npm rebuild

[psethwick]

sudo npm gives me the heebie jeebies