Is there a way to set global configuration?

Editor plugins don’t always have ways to pass configuration to the process they call.

For example, in order to set the vim plugin neoformat to tell prettier to use single quotes, I’ve had to fork the plugin.

Other vim plugins for linting, for example, aren’t an issue because we have eslintrc.

I appreciate the complexity involved in having a prettierrc file (the spelling alone is awkward!) and I agree with the spirit of not adding too many options, but is there a way to set a global configuration that prettier could always use?

[lydell]

What about being able to specify options in package.json?

{
  "name": "some-package",
  "prettierConfig": {
    "printWidth": 71,
    "tabWidth": 4,
    "singleQuote": true,
    "trailingComma": true,
    "bracketSpacing": false,
    "parser": "flow"
  },
  "dependencies": {
    "prettier": "0.11.0"
  }
}

It’s easy to read the closest package.json with read-pkg-up;

const readPkgUp = require("read-pkg-up");
let pkg;
try {
  pkg = readPkgUp.sync({normalize: false}).pkg;
} catch (e) {
  console.error(e);
}
const globalOptions = (pkg && pkg.prettierConfig) || {};

Or simply always from ./package.json:

let pkgString;

try {
  pkgString = fs.readFileSync("./package.json", "utf8");
} catch (e) {
  // Ignore no package.json found.
}

let pkg;

if (pkgString) {
  try {
    pkg = JSON.parse(pkgString);
  } catch (e) {
    console.error(e);
  }
}

const globalOptions = (pkg && pkg.prettierConfig) || {};

[evanliomain]

@jlongster ENV variable is a pain to use unlike a file configuration. Consider a project :

• which can be run on windows, mac and linux ;
• which is edited on vscode, vim, textmate, notepad (etc) according developper flavour

Consider you have several project on your laptop, and each one with a different configuration (because of different team)

A prettierrc, tracked in the version control (like git) is the nice way to share the configuration :

• a new developper have it when he checkout it
• it’s version controlled, with all benefit (history, PR review …)

ENV variable need a configuration for each team’s developper. It a big break to adopt it in a project.