Missing Types in @salesforce/lightning-types

Abierto
  • ¿Algo no está bien?
#3,683 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, node.js, typescript
Área
developer-experience, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Sin datos de lenguaje
Estrellas
575
Forks
80
Merge medio
11 h 37 min
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de forcedotcom/cli

Todos los issues de forcedotcom/cli

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.