Skip to content

Runtime error in resolveConfig.js when bundled with Webpack + Babel #10675

@zhengxs2018

Description

@zhengxs2018

Hi there,

We’re encountering a runtime error after bundling our project with Webpack and Babel. It seems that a recent plugin update is injecting extra code into the syntax combining arrow functions and default exports, which breaks the compiled output.

Source Code:

Image

Compiled Output (Bundled):

Image

Any module using an arrow function as a default export triggers this issue. We are still investigating exactly which plugin is causing the injection, but the symptom is consistent.

Image

We noticed that resolveConfig.js was introduced in Axios v1.7.0. Because of this bug, we’ve had to pin our Axios version to 1.6.x as a temporary workaround.

It would be great if resolveConfig.js could be refactored or handled in a way that avoids this compatibility issue with common bundler/transpiler setups.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions