Missing Types in @salesforce/lightning-types

Offen
  • Stimmt etwas nicht?
#3,683 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
javascript, node.js, typescript
Bereich
developer-experience, tooling

Rechercherichtung

Start by checking the Salesforce TypeScript guidance linked in the issue and the published @salesforce/lightning-types package to see how platform module declarations are organized. The issue names missing types for lightning/platformShowToastEvent and lightning/navigation, but does not identify the package source repository or its contribution process. Done means both modules resolve with useful type information in an LWC, though maintainers may need to confirm where the package is maintained.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

investigating validated
Before You Submit
  • I'm using the latest version of Salesforce CLI
  • I've searched the existing issues
  • I've run sf doctor to diagnose common issues
Related Issue

No response

Command

nom install @salesforce/lightning-types

Org Type

Not applicable

Did this work before?

No, this is a new bug

Last Working Version

No response

Summary

Please route this to the correct channel.

When trying to use type checking in JS or TS I've found that I can't find types for a few packages available from any of the Salesforce extensions or packages, specifically the expected @salesforce/lightning-types package.

The first few I found:

  • lightning/platformShowToastEvent
  • lightning/navigation

Please help me get these in front of whomever maintains those packages so they can be added. I'm happy to submit initial types that I've added to my own project though they may be incomplete. If there is a better channel to submit these issues please let me know.

Note: It would be amazing if that package were made available as an open-source project so the community could take a more direct hand in contributing and maintaining.

Repository to Reproduce

No response

Steps to reproduce

Following the instructions at
https://developer.salesforce.com/docs/platform/lwc/guide/ts.html#manually-install-the-lightning-types-package

Then use either of the two packages in an LWC. The type information is unable to resolve.

If you'd like clearer errors you can enable type checking for the JS components by adding the Compiler Options "checkJS" = true in your jsconfig.json, this will cause the import to display as unresolvable.

Expected Result

I would like the @salesforce/lightning-types package to provide type information for all of the platform provided packages. Making is so I can provide a better development experience and enforce type safety, improving the quality of the components we build.

Actual Result

The types do not resolve and the type checking throws an error and the IDE is unable to provide completion helps.

Error Message
System Information
{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.157.8",
  "nodeVersion": "node-v26.13.0",
  "osVersion": "Darwin 27.2.0",
  "rootPath": "/Users/heber/.local/share/sf/client/2.157.8-b36e90e",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 4.0.6 (core)",
    "@oclif/plugin-commands 5.0.6 (core)",
    "@oclif/plugin-help 7.0.6 (core)",
    "@oclif/plugin-not-found 4.0.7 (core)",
    "@oclif/plugin-plugins 7.0.13 (core)",
    "@oclif/plugin-search 2.0.9 (core)",
    "@oclif/plugin-update 5.0.10 (core)",
    "@oclif/plugin-version 3.0.7 (core)",
    "@oclif/plugin-warn-if-update-available 4.0.5 (core)",
    "@oclif/plugin-which 4.0.6 (core)",
    "@salesforce/cli 2.157.8 (core)",
    "agent 2.2.3 (core)",
    "apex 4.4.4 (core)",
    "api 2.0.24 (core)",
    "auth 6.0.0 (core)",
    "data 5.1.24 (core)",
    "deploy-retrieve 4.3.2 (core)",
    "info 4.0.22 (core)",
    "lightning-dev 6.2.22 (user) published 20 days ago (Thu Oct 15 2026)",
    "limits 4.0.6 (core)",
    "marketplace 2.0.23 (core)",
    "org 7.0.10 (core)",
    "packaging 3.0.17 (user) published 9 days ago (Mon Oct 26 2026)",
    "schema 4.0.16 (core)",
    "settings 3.0.22 (core)",
    "signups 3.0.12 (user) published 18 days ago (Sun Oct 18 2026) (latest is 3.0.13)",
    "sobject 2.0.20 (core)",
    "telemetry 4.2.4 (core)",
    "templates 57.5.0 (core)",
    "trust 4.0.28 (core)",
    "user 6.0.6 (core)",
    "sfdx-git-delta 6.45.1 (user) published 132 days ago (Fri Jun 26 2026)"
  ]
}
Additional Information

No response

Screenshots or Log Files

No response

Vorherrschende Sprache
Keine Sprachdaten
Sterne
575
Forks
80
Ø Merge
5 Std. 58 Min.
Gemergte PRs (30 T.)
4

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus forcedotcom/cli

Alle Issues in forcedotcom/cli

Ähnliche Issues

Weitere Issues zu DevTools

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.