Next.js: `next build` on canary using full path in transpiled require statements

[kylealwyn]

• [x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

next build does not include absolute path to node module

Current Behavior

next build includes absolute path in transpiled require path

Steps to Reproduce (for bugs)

Correct

yarn add [email protected]
next build

# Transpiled output
var _extends2 = require('babel-runtime/helpers/extends');

Incorrect

yarn add next@canary
next build

# Transpiled output
var _extends2 = require('/Users/kyle/projects/test/node_modules/babel-runtime/helpers/extends');

Context

Unable to deploy to lambda using up due to up building locally and uploading zip file to s3 rendering absolute paths invalid

Your Environment

| Tech | Version |
|---------|---------|
| next | canary |
| node | 8.9.0 |
| OS | macos 10.13.2 |

[mrtnzlml]

Same problem - see ^^ postmortem. Also serverless environment deployed from Travis-CI.

[juancampa]

FWIW the problem seems to be: https://github.com/zeit/next.js/blob/85f341c9d834114be1127cf73a04bc3517cc2f67/server/build/webpack/utils.js#L4

[timneutkens]

Created a pull request 🙏 I had actually already fixed the babel-runtime issue. The pages issue is a new one 👍