prettier support for already-installed node.js packages

Open
#675 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
build-system, tooling

Research direction

Start by locating the existing Prettier configuration and the Gradle integration that manages Node.js dependencies. Review how package.json and package-lock.json are currently handled, then define the command-line inputs and dependency wiring needed for already-installed packages. Done means a documented, usable integration with clear caching behavior.

Written by the indexing model from the issue text.

Description

enhancement

For projects which are already using gradle to manage node.js and install deps with package.json, it would be nice if our prettier config could hook into that. Maybe if it had an arg where you passed the node executable, and another for passing package-lock.json for caching, and it was on you (somehow) to make sure that the dependencies were wired correctly. Getting the ergonomics right is key, and also difficult...

Dominant language
Java
Stars
5.7k
Forks
560
Avg merge
1d 13h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

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 diffplug/spotless

All issues in diffplug/spotless

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.