fix(gatsby): pin webpack to fix unexpected token error during build #11640
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This addresses gatsbyjs#11198. There's a regression bug webpack/webpack#8656 affecting 4.29.0 through at least 4.29.3 which causes errors like this during `gatsby build`. Error: ./.cache/async-requires.js 8:11 Module parse failed: Unexpected token (8:11) You may need an appropriate loader to handle this file type. | exports.components = { | "component---frontend-components-main-js": function componentFrontendCompo nentsMainJs() { > return import("/home/circleci/project/frontend/components/main.js" | /* webpackChunkName: "component---frontend-components-main-js" */ | ); @ ./.cache/production-app.js 18:0-45 21:23-36 26:23-36
paulmelnikow
force-pushed
the
gatsby/downgrade-webpack
branch
from
09c143c
to
56e0409
Compare
DSchau
reviewed
Feb 8, 2019
Co-Authored-By: paulmelnikow <github@paulmelnikow.com>
DSchau
changed the title
gatsby build problem
DSchau
approved these changes
Feb 8, 2019
|
gurpreet-hanjra
pushed a commit
to gurpreet-hanjra/gatsby
that referenced
this pull request
Feb 14, 2019
…atsbyjs#11640) ## Description This addresses gatsbyjs#11198. There's a regression bug webpack/webpack#8656 affecting 4.29.0 through at least 4.29.3 which causes errors like this during `gatsby build`. Error: ./.cache/async-requires.js 8:11 Module parse failed: Unexpected token (8:11) You may need an appropriate loader to handle this file type. | exports.components = { | "component---frontend-components-main-js": function componentFrontendCompo nentsMainJs() { > return import("/home/circleci/project/frontend/components/main.js" | /* webpackChunkName: "component---frontend-components-main-js" */ | ); @ ./.cache/production-app.js 18:0-45 21:23-36 26:23-36 <!-- Have any questions? Check out the contributing docs at https://gatsby.app/contribute, or ask in this Pull Request and a Gatsby maintainer will be happy to help :) --> ## Related Issues - Addresses gatsbyjs#11198 - Related to webpack/webpack#8656
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This addresses #11198.
There's a regression bug webpack/webpack#8656 affecting 4.29.0 through at least 4.29.3 which causes errors like this during
gatsby build.Error: ./.cache/async-requires.js 8:11
Module parse failed: Unexpected token (8:11)
You may need an appropriate loader to handle this file type.
| exports.components = {
| "component---frontend-components-main-js": function componentFrontendCompo nentsMainJs() {
| /* webpackChunkName: "component---frontend-components-main-js" */
| );
@ ./.cache/production-app.js 18:0-45 21:23-36 26:23-36
Related Issues
async-requiresafter upgrade to 2.0.84 #11198import()fails in 4.29.0 (Compilation issue, related to dynamic import) webpack/webpack#8656