Module parse failed: Unexpected token

[eward957]

Describe the bug

Module parse failed: Unexpected token (3:55)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
import _regeneratorRuntime from"/data_b/work/gitlab-runner/builds/622b053b/0/lala/test/node_modules/babel-preset-react-app/node_modules/@babel/runtime/regenerator";import _objectSpread from"/data_b/work/gitlab-runner/builds/622b053b/...

occur a fatal error when building production version, but development correctly; :( ...

it seems to generated code of babel has error, between 'from' and '"/data_b/work/gitlab-runn' in error message haven't blank????

[eward957]

yarn.lock indicate two @babel/core package was installed, @7.12.3 and @7.15.0

????

[eward957]

temporal solution

i try to change babel's compact option to false, this error disappear.....

https://github.com/facebook/create-react-app/blob/main/packages/react-scripts/config/webpack.config.js#L438

[tep-pl]

+1. we're facing the same issue for few hours as well, effectively getting CI builds blocked

[tep-pl]

in our case the problem seems to be the following code:

const SomeContext = React.createContext(null);

export const SomeContextProvider = ({ children }) => {
    ...
    return (
        <SomeContext.Provider value={value}>
            {children}
        </SomeContext.Provider>
    );
};

getting transpiled to something like:
.... var SomeContext=/*#__PURE__*/React.createContext(null);SomeContext.displayName="SomeContext"export var SomeContextProvider=function SomeContextProvider(_ref) ....

note the missing semicolon between SomeContext.displayName="SomeContext" and export var SomeContextProvider

[eward957]

+1. we're facing the same issue for few hours as well, effectively getting CI builds blocked

I guess: some denpendencies are incompatible with babel/[email protected], but i don't know which one...

so, I upgrede all babel's plugins and presets, ci building working correctly now :(.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.