Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Ignore Node modules by default (to match CLI behaviour)

See original GitHub issue

Prettier’s CLI ignores node_modules by default. However, for this VSCode extension, users must manually specify node_modules in a .prettierignore.

Could we make this extension’s default behaviour match that of the CLI, which is to ignore node_modules?

Issue Analytics

State:
Created 5 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

OliverJAshcommented, Aug 13, 2018

Debugging (e.g. adding console.logs), and then occasionally I “commit” changes to node_modules via patch-package.

0reactions

github-actions[bot]commented, Apr 12, 2020

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

Webpack not excluding node_modules - Stack Overflow

From your config file, it seems like you're only excluding node_modules from being parsed with babel-loader , but not from being bundled.

config - npm Docs

Run npm config ls -l to see a set of configuration parameters that are internal to npm, and are defaults if nothing else...

Configuration options | Yarn - Package Manager

This overrides the default behavior of comparing against master, origin/master, upstream/master, main, origin/main, and upstream/main. Supports git branches, ...

Command-line API | Node.js v19.3.0 Documentation

Node. js comes with a variety of CLI options. These options expose built-in debugging, multiple ways to execute scripts, and other helpful runtime...

CLI - Prettier

Prettier CLI will ignore files located in node_modules directory. To opt out from this behavior, use --with-node-modules flag.