Skip to content

No details provided when plugin fails to be loaded by experimental CLI #17715

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Environments:

  • Prettier Version: 3.6.2
  • Running Prettier via: CLI
  • Runtime: Node.js v24
  • Operating System: macOS
  • Prettier plugins (if any): prettier-plugin-curly

Steps to reproduce:

With prettier-plugin-curly added as a plugin, run with the new experimental CLI:

prettier --experimental-cli
  The plugin "prettier-plugin-curly" could not be loaded

Minimum reproduction: https://github.com/JoshuaKGoldberg/repros/tree/prettier-experimental-cli-plugin-curly

Expected behavior:

If there's an exception / failure loading a plugin, it'd be nice to see more details. Is there an error stack? Failure to import? Something else?

Actual behavior:

Even with --log-level debug, no additional stack traces, error details, etc. are reported.

Regardless of whether there's a bug around this specific plugin, the lack of debug information about the failure is itself a bug I think. Or at least a missing feature.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:duplicateIssues that are a duplicate of a previous issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy