New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
next build
on canary using full path in transpiled require statements
#3533
Comments
kylealwyn
changed the title
Jan 11, 2018
next build
on canary using full path in transpiled requiresnext build
on canary using full path in transpiled require statements
Same problem - see ^^ postmortem. Also serverless environment deployed from Travis-CI. |
FWIW the problem seems to be: https://github.com/zeit/next.js/blob/85f341c9d834114be1127cf73a04bc3517cc2f67/server/build/webpack/utils.js#L4 |
This was referenced Feb 6, 2018
Created a pull request 🙏 I had actually already fixed the babel-runtime issue. The pages issue is a new one 👍 |
1 task
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected Behavior
next build
does not include absolute path to node moduleCurrent Behavior
next build
includes absolute path in transpiled require pathSteps to Reproduce (for bugs)
Correct
Incorrect
Context
Unable to deploy to lambda using up due to
up
building locally and uploading zip file to s3 rendering absolute paths invalidYour Environment
The text was updated successfully, but these errors were encountered: