Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

special/webpack: entries should also be scanned #446

Closed
sveyret opened this issue Nov 1, 2019 · 1 comment
Closed

special/webpack: entries should also be scanned #446

sveyret opened this issue Nov 1, 2019 · 1 comment

Comments

@sveyret
Copy link
Contributor

sveyret commented Nov 1, 2019

Bug Description

In the entry section of webpack configuration, we may also specify dependencies which should be scanned. It is the case, for example, of the @babel/polyfill, of special fonts, etc.

Code snippets

Where the dependency is used:

module.exports = {
  entry: [
    '@babel/polyfill',
    'typeface-roboto',
    './src/index.ts',
    './src/images/favicon.png'
  ]
}

Where the dependency is listed in package.json:

"dependencies": {
  "typeface-roboto": "0.0.75"
},
"devDependencies": {
  "@babel/polyfill": "7.6.0",
}

Versions

  • node -v: v8.12.0
  • npm -v: 6.4.1
  • depcheck --version: 0.8.4

Extra info

I am currently working on a PR for this issue.

rumpl pushed a commit that referenced this issue Nov 1, 2019
* special/webpack: Manage TypeScript webpack definition

Issue #246

* special/webpack: Scan webpack entries for dependencies

Issue #446

* special/webpack: Detect babel-loader presets

Issue #448
@rumpl rumpl closed this as completed Nov 1, 2019
@rumpl
Copy link
Member

rumpl commented Nov 1, 2019

Closed with #449

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants