chore: update @bitdev/react.generators.react-templates to ^6.0.9 by zkochan · Pull Request #10619 · teambit/bit

zkochan · 2026-08-14T16:27:25Z

Proposed Changes

qodo-free-for-open-source-projects · 2026-08-14T16:28:13Z

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Tip of the day

💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Previous reviews

Review updated until commit 1ad9b46 ⚖️ Balanced

Results up to commit e15bf5f

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit 0aac64d

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit a26ccb3

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit 8b6bd04

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit 1c7af92

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit 8a9e32a

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.
### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.
### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]
### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit cfea426

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Webpack template unregistered 🐞 Bug ≡ Correctness

Description

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned
by getTemplates(), so the Generator aspect will no longer expose that template for component
generation under this env.

Code

scopes/react/react/react.templates.ts[L20-21]

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),

Evidence

The current getTemplates() implementation builds templates from TemplateList.from([...]) and no
longer includes the webpack template in that list. That list is what ReactMain registers into the
Generator aspect, so removing an entry removes the template from generator-exposed templates.

scopes/react/react/react.templates.ts[13-26]
scopes/react/react/react.main.runtime.ts[470-478]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist.

### Issue Context
`getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect.

### Fix Focus Areas
- scopes/react/react/react.templates.ts[1-21]
- scopes/react/react/react.main.runtime.ts[470-478]

### Expected fix
- If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list.
- If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit 99eee49

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

qodo-free-for-open-source-projects · 2026-08-14T16:28:24Z

PR Summary by Qodo

Update pnpm lockfile

⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Regenerate pnpm lockfile to refresh resolved dependency graph and metadata.
• Ensure installs remain reproducible with the current workspace overrides/resolution.

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin pnpm version via packageManager field

➕ Reduces lockfile churn caused by pnpm version differences across machines/CI
➕ Improves reproducibility and review stability
➖ Requires aligning developer environments and CI to the pinned pnpm version
➖ May require tooling changes (corepack enable / CI setup adjustments)

2. Lockfile-only refresh (avoid dep upgrades)

➕ Minimizes risk of accidental dependency bumps
➕ Keeps PR strictly about normalization/re-resolution
➖ May not capture intended dependency upgrades if those were desired
➖ Still produces churn if the underlying resolver behavior changed

Recommendation: The lockfile update approach is fine, but reviewers should confirm whether changes are purely re-resolution vs. actual version movement. If lockfile-only PRs are frequently noisy, consider pinning the pnpm version (e.g., via a packageManager field + corepack) to stabilize future diffs.

Files changed (1) +21352 / -28965

Other (1) +21352 / -28965

pnpm-lock.yamlRegenerate pnpm dependency lockfile +21352/-28965

Regenerate pnpm dependency lockfile

• Updates the workspace dependency resolution snapshot captured by pnpm, including resolved versions, transitive graph entries, and associated lock metadata (e.g., integrity/resolution details). This is intended to keep installs consistent and reproducible for CI and developers.

pnpm-lock.yaml

qodo-free-for-open-source-projects · 2026-08-14T17:07:21Z

-  ReactWebpackTemplate.from({ env: 'bitdev.react/react-env' }),
-  // ReactWebpackAppTemplate.from({ env: 'bitdev.react/react-env' }),
  ReactJSComponentTemplate.from({ env: 'bitdev.react/react-env' }),
  ReactEnvTemplate.from(),
 ]);


1. Webpack template unregistered 🐞 Bug ≡ Correctness

scopes/react/react/react.templates.ts removes ReactWebpackTemplate from the templates returned by getTemplates(), so the Generator aspect will no longer expose that template for component generation under this env.

Agent Prompt

### Issue description The React env no longer registers the webpack-based generator template (`ReactWebpackTemplate`). This removes it from the template set exposed via `generator.registerComponentTemplate(...)`, which can break template selection/generation flows that expect it to exist. ### Issue Context `getTemplates()` defines the full list of component templates, and `ReactMain` registers that list with the Generator aspect. ### Fix Focus Areas - scopes/react/react/react.templates.ts[1-21] - scopes/react/react/react.main.runtime.ts[470-478] ### Expected fix - If webpack-based generation is still supported: re-add `ReactWebpackTemplate` import and its `.from(...)` entry in the `TemplateList.from([...])` list. - If it is intentionally deprecated: add an explicit replacement path (e.g., documented Vite template), and update the PR description/changelog so consumers understand the removal and can migrate.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

qodo-free-for-open-source-projects · 2026-08-14T17:07:23Z

Code review by qodo was updated up to the latest commit cfea426

qodo-free-for-open-source-projects · 2026-08-18T12:23:48Z

Code review by qodo was updated up to the latest commit 8a9e32a

qodo-free-for-open-source-projects · 2026-08-18T13:05:16Z

Code review by qodo was updated up to the latest commit 1c7af92

qodo-free-for-open-source-projects · 2026-08-18T13:44:16Z

Code review by qodo was updated up to the latest commit 8b6bd04

qodo-free-for-open-source-projects · 2026-08-18T14:49:57Z

Code review by qodo was updated up to the latest commit a26ccb3

qodo-free-for-open-source-projects · 2026-08-18T14:59:18Z

Code review by qodo was updated up to the latest commit 0aac64d

qodo-free-for-open-source-projects · 2026-08-18T18:15:22Z

Code review by qodo was updated up to the latest commit e15bf5f

qodo-free-for-open-source-projects · 2026-08-19T08:40:23Z

Code review by qodo was updated up to the latest commit 1ad9b46

qodo-free-for-open-source-projects Bot reviewed Aug 14, 2026

View reviewed changes

fix: update react-templates version spec

8a9e32a

zkochan force-pushed the update-lockfile branch from cfea426 to 8a9e32a Compare August 18, 2026 12:22

zkochan changed the title ~~chore: update lockfile~~ chore: update @bitdev/react.generators.react-templates to ^6.0.9 Aug 18, 2026

GiladShoham approved these changes Aug 18, 2026

View reviewed changes

Merge branch 'master' into update-lockfile

1c7af92

Merge branch 'master' into update-lockfile

8b6bd04

Merge branch 'master' into update-lockfile

a26ccb3

Merge branch 'master' into update-lockfile

0aac64d

Merge branch 'master' into update-lockfile

e15bf5f

GiladShoham approved these changes Aug 19, 2026

View reviewed changes

Merge branch 'master' into update-lockfile

1ad9b46

GiladShoham enabled auto-merge (squash) August 19, 2026 08:39

github-actions Bot mentioned this pull request Aug 19, 2026

Merge Queue Dashboard #10562

Open

Merge branch 'master' into update-lockfile

1a1f8fd

GiladShoham merged commit 6cd39f2 into teambit:master Aug 19, 2026
14 checks passed

Navigation Menu

Uh oh!

chore: update @bitdev/react.generators.react-templates to ^6.0.9 - #10619

chore: update @bitdev/react.generators.react-templates to ^6.0.9#10619
GiladShoham merged 8 commits into
teambit:masterfrom
zkochan:update-lockfile

zkochan commented Aug 14, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 14, 2026 •

edited

Loading

Great, no issues found!

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 14, 2026

Uh oh!

qodo-free-for-open-source-projects Bot Aug 14, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 14, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 19, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

zkochan commented Aug 14, 2026

Proposed Changes

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Great, no issues found!

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 14, 2026

PR Summary by Qodo

Uh oh!

qodo-free-for-open-source-projects Bot Aug 14, 2026

Choose a reason for hiding this comment

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 14, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 18, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 19, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

qodo-free-for-open-source-projects Bot commented Aug 14, 2026 •

edited

Loading