Skip to content

Why not supporting an object for webpackConfig parameter? #144

Description

@Awen-hub

Now, webpackConfig parameter just supports the file path which is not convenient as an object. So Why not supporting an object for webpackConfig parameter just like the tsConfig parameter?

example:

const tree = dependencyTree({
  filename: `xxx/index.tsx`,
  directory: `xxx/src`,
  filter: (path) => path.indexOf("node_modules") === -1, 
  webpackConfig: {
    resolve: {
      extensions: [".js", ".jsx", ".tsx", ".ts"],
    },
  }
});

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions