Removes duplicate module warnings when vendoring Python packages

[dom96]

Wrangler would output "Ignoring duplicate module" for each .txt file inside python_modules. This PR fixes this.

Turns out that this was happening because parseRules adds some default rules.

---

• Tests
  • Tests included
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: bug fix
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: not in v3

---

Test Plan

$ pnpm build -F wrangler
$ node /Users/dominik/repos/workers-sdk/packages/wrangler/wrangler-dist/cli.js dev

Before:

▲ [WARNING] Ignoring duplicate module: webtypy-0.1.7.dist-info/top_level.txt (text)
Attaching additional modules:
┌─────────────────────┬──────┬─────────────┐
│ Name                │ Type │ Size        │
├─────────────────────┼──────┼─────────────┤
│ Vendored Modules    │      │ 8941.49 KiB │
├─────────────────────┼──────┼─────────────┤
│ Total (383 modules) │      │ 8941.49 KiB │
└─────────────────────┴──────┴─────────────┘

After:

Attaching additional modules:
┌─────────────────────┬──────┬─────────────┐
│ Name                │ Type │ Size        │
├─────────────────────┼──────┼─────────────┤
│ Vendored Modules    │      │ 8941.49 KiB │
├─────────────────────┼──────┼─────────────┤
│ Total (383 modules) │      │ 8941.49 KiB │
└─────────────────────┴──────┴─────────────┘

[changeset-bot]

🦋 Changeset detected

Latest commit: 5268b77

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main dominik/fix-duplicate-python-vendor-warnings might be a good starting point.

Notes:

• your PR branch should be named v3-backport-11284
• add the skip-v3-pr label to the current PR to stop this workflow from failing

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11284

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11284

miniflare

npm i https://pkg.pr.new/miniflare@11284

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11284

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11284

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11284

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11284

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11284

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11284

wrangler

npm i https://pkg.pr.new/wrangler@11284

commit: 5268b77

[petebacondarwin]

Yeah calling parseRules() is a bit overkill here

[dom96]

@petebacondarwin Rebased, hopefully now this is mergeable 🙏