xojs/xo

Projects in a Turborepo monorepo not using workspace package.json config

Open

#733 opened on Oct 11, 2023

View on GitHub
 (3 comments) (3 reactions) (0 assignees)JavaScript (7,430 stars) (344 forks)batch import
bughelp wanted

Description

Hello,

I have a very simple XO configuration I'd like to share between all the packages and apps in my Turborepo monorepo:

"xo": {
  "prettier": true,
  "rules": {
    "import/extensions": 0
  }
}

The project README states that I should just need one version of this in the root package.json file:

However, I'm seeing linting errors in each of my packages if I don't have this XO config in every package.json. Have I configured something incorrectly?

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of XO linterUnderstanding of monorepo structureFamiliarity with Turborepo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Investigate how XO resolves configuration in monorepo contexts, specifically with Turborepo. Check if the root package.json config is being ignored due to workspace boundaries. Look at XO's documentation on monorepo support and any known issues. Consider replicating the setup in a minimal Turborepo monorepo to confirm the bug. Check existing linked discussions or maintainer comments for insights.