Skip to content

Avoid using internal webpack API #4747

@alexander-akait

Description

@alexander-akait

Clear and concise description of the problem

I found a lot of places with require("webpack/lib/something"), they are private and can be changed (moved to other directory, renamed, etc). There is a public API under compiler.webpack.something and it is a stable API and will not changed between versions.

Ref: webpack/webpack#20985

We can add more things if something missed in compiler.webpack, feel free to list here and we will add them

Suggested solution

Don't use private methods.

Alternative

No response

Additional context

No response

Validations

  • Read the Contributing Guidelines.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

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