Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can't deploy a TypeScript LWC component to pre-release scratch org

Open
  • Is something wrong?
#3,011 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

Reproduce the failure with a preview scratch org, an API v62.0 project, a Lightning Web Component using a .ts file, and sf project deploy start. Start by tracing the deployment handling for TypeScript LWC components; done means the component deploys successfully and the reported missing-bundle error no longer occurs.

Written by the indexing model from the issue text.

Description

bug

NOTE: Logging this after discussion with Vivek Chawla in Slack.

The short version is that I've created a preview scratch org and an API v62.0 project, then I've created an LWC component with a valid .ts file instead of a .js file. When I try to deploy the project to the scratch org, I get:

$ sf project deploy start
Deploying v62.0 metadata to <redacted> using the v62.0 SOAP API.
Deploy ID: <redacted>
Status: Failed | ████████████████████████████████████████ | 1/1 Components | Errors: 1

Component Failures [1]
===================================================================================
| Type  Name        Problem                                             Line:Column 
| ───── ─────────── ─────────────────────────────────────────────────── ─────────── 
| Error tsComponent Cannot find Lightning Component Bundle tsComponent.
Note that I'm on the latest GA build of the CLI:

The same behavior occurs on the stable (@salesforce/cli/2.57.7 win32-x64 node-v20.16.0) and nightly (@salesforce/cli/2.59.5 win32-x64 node-v20.17.0) CLI builds.

System Information
CLI:
@salesforce/cli/2.59.5 win32-x64 node-v20.17.0

Plugin Version:
@oclif/plugin-autocomplete 3.2.3 (core)
@oclif/plugin-commands 4.0.14 (core)
@oclif/plugin-help 6.2.11 (core)
@oclif/plugin-not-found 3.2.20 (core)
@oclif/plugin-plugins 5.4.7 (core)
@oclif/plugin-search 1.2.8 (core)
@oclif/plugin-update 4.5.6 (core)
@oclif/plugin-version 2.2.12 (core)
@oclif/plugin-warn-if-update-available 3.1.15 (core)
@oclif/plugin-which 3.2.13 (core)
@salesforce/cli 2.59.5 (core)
apex 3.4.9 (core)
api 1.2.1 (core)
auth 3.6.56 (core)
data 3.6.5 (core)
deploy-retrieve 3.12.7 (core)
info 3.4.6 (core)
lightning-dev 1.1.1 (user)
limits 3.3.30 (core)
marketplace 1.2.25 (core)
org 4.5.8 (core)
packaging 2.8.4 (core)
schema 3.3.29 (core)
settings 2.3.19 (core)
sobject 1.4.35 (core)
source 3.5.19 (core)
telemetry 3.6.12 (core)
templates 56.3.18 (core)
trust 3.7.27 (core)
user 3.5.29 (core)
@salesforce/sfdx-scanner 4.2.0 (user)

SF ENV. VARS.
SF_AUTOUPDATE_DISABLE,true
SF_BINPATH,C:\Users\Scott\AppData\Local\sf\client\bin\sf
SF_DISABLE_AUTOUPDATE,true
SF_DISABLE_TELEMETRY,true
SF_TARGET_DEV_HUB,ic-dev-hub
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.

Windows: true
Shell: cmd.exe
Channel: stable
Diagnostics

✅ pass - salesforcedx plugin isn’t installed
✅ pass - you don't have any linked plugins
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
❌ warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - can access: https://test.salesforce.com
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
✅ pass - using latest or latest-rc CLI version
❌ fail - [@salesforce/plugin-auth] CLI supports v2 crypto
✅ pass - [@salesforce/plugin-auth] CLI using stable v1 crypto

Dominant language
No language data
Stars
571
Forks
80
Avg merge
2d 21h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/cli

All issues in forcedotcom/cli

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.