🐛 Webpack entry: {name: './extension-less-file'} not supported

[fregante]

Prerequisites

• I'm using the latest version
• I've read the relevant documentation
• I've searched for existing issues
• I've checked the list of known issues
• I've read the issue reproduction guide

Reproduction url

Non-minimal repro: https://github.com/pixiebrix/pixiebrix-extension/blob/92cbf5c2c132fc5618be7f0855266daac99f1f88/webpack.config.mjs#L112-L142

Reproduction access

• I've made sure the reproduction is publicly accessible

Description of the issue

I'm creating some issues for tracking the bugs I found. I'll minimize the repro as necessary.

I reported this a year ago, but the reason was not immediately clear because knip does not report invalid entry points (this seems to be a common cause for trouble).

If webpack.config.js exports this, knip can't resolve them

module.exports = {
  entry: {
    background: './src/background/background',
    contentScript: './src/contentScript/contentScript',
  }
}

but it works if I add the extensions:

module.exports = {
  entry: {
    background: './src/background/background.ts',
    contentScript: './src/contentScript/contentScript.tsx',
  }
}

I think webpack can resolve certain extensions natively (.js) but extra config may be required to resolve .ts and .tsx. This works correctly in webpack:

module.exports = {
  entry: {
    background: './src/background/background',
    contentScript: './src/contentScript/contentScript',
  }
  resolve: {
    extensions: [".ts", ".tsx", ".jsx", ".js", ".mjs"],
  }
}

You can see extension-less entries in the docs: https://webpack.js.org/configuration/entry-context/#dynamic-entry

[webpro]

This hasn't been reported before as I guess most configurations just use the full filename including the extension.

[webpro]

🚀 This issue has been resolved in v5.44.5. See Release 5.44.5 for release notes.

Using Knip in a commercial project? Please consider becoming a sponsor.

[fregante]

I can confirm that did it! Thank you Lars