ReferenceError: Cannot access x before initialization

I tried implementing this and I got an error like in the subject. The reason is that the exports are accessing constants defined below them.

This is what the result looks like:

        "use strict";
        __webpack_require__.r(__webpack_exports__);
        /* WEBPACK VAR INJECTION */
        (function(__react_refresh_utils__, __react_refresh_error_overlay__) {
            /* harmony export (binding) */
            __webpack_require__.d(__webpack_exports__, "BoxWithLine", function() {
                return BoxWithLine;
            });

      
[...]

            __webpack_require__.$Refresh$.runtime = __webpack_require__(/*! react-refresh/runtime */
            "./node_modules/.pnpm/react-refresh@0.8.3/node_modules/react-refresh/runtime.js");
            __webpack_require__.$Refresh$.setup(module.i);

[...]

            const BoxWithLine = /*#__PURE__*/
            Object(styled_components__WEBPACK_IMPORTED_MODULE_13__["default"])(app_components_Layout__WEBPACK_IMPORTED_MODULE_2__["Box"]).withConfig({
                displayName: "Page__BoxWithLine",
                componentId: "sc-174cupy-0"
            })(["\n\tborder-color: transparent;\n\tborder-bottom: 1px solid ", ";\n"], app_styles__WEBPACK_IMPORTED_MODULE_6__["grey10"]);

I put the plugins at the bottom of the plugins array for both webpack and babel.

[pmmmwh]

Hi, I did a bit of digging and I think this is definitely either caused by:

1. Unnamed default exports with namespaces
2. Circular dependencies

Webpack tries to concatenate modules and hoist them in the correct order, but in rare cases this will fail and yield this error.

[kimbaudi]

@wmertens - I was also facing a similar situation where I had a single const that broke on production build due to a circular dependency. Changing the const to a var also worked for me, but I don’t think that is the correct way to handle that situation. Instead, I moved the const into a new module and I can still use const and the ReferenceError went away. I was able to solve the issue by looking at https://github.com/webpack/webpack/issues/9173#issuecomment-494903242