Prettier plugin

apotheke registers as a Prettier plugin that hooks preprocess. Prettier hands it the source, apotheke rewrites the import block, and Prettier then formats the result. One command, correct order, no fighting between two tools.

.prettierrc.json

{
    "plugins": ["apotheke"]
}

That is the whole setup. prettier --write now organises imports.

Ordering matters — apotheke goes last

apotheke must be the last plugin

Prettier v3 does not merge plugins that define the same parser: the last one wins outright. apotheke deliberately chains to the previous plugin's preprocess before running its own, so it composes correctly — but only if nothing is listed after it. Any plugin placed later silently replaces apotheke and imports stop being organised.

Correct

{
    "plugins": ["prettier-plugin-tailwindcss", "apotheke"]
}

Broken — tailwind wins, apotheke never runs

{
    "plugins": ["apotheke", "prettier-plugin-tailwindcss"]
}

There is no warning when you get this wrong. If imports stop moving after adding a plugin, check the array order first.

Which files it touches

The plugin overrides the typescript, babel, babel-ts and babel-flow parsers, which covers .ts, .tsx, .js, .jsx and .mjs. Other Prettier parsers — CSS, JSON, Markdown, YAML — pass through untouched.

Code blocks in Markdown and MDX are left alone

Prettier formats fenced code blocks inside documents by handing them to the embedded language's parser, which would otherwise route your documentation through apotheke. That is almost never wanted: a ts block showing imports in a deliberately messy "before" state would be silently rewritten into the organised version, and the example would stop demonstrating anything.

apotheke detects the document container and returns those snippets untouched, so prettier --write on a .md or .mdx file reformats the prose and leaves every code block exactly as written.

Your .ts and .tsx files are unaffected — only snippets embedded in a document are skipped.

Failures are silent by design

If the plugin throws for any reason — no config found, a syntax error in apotheke.config.mjs, an unparseable source file — it catches the error and returns the file unchanged. Prettier never breaks because of apotheke.

The trade-off is that a broken config looks identical to a working one that had nothing to do. When imports are not moving and the plugin order is right, run the CLI on the same file — it reports errors instead of swallowing them:

npx apotheke --diff src/App.tsx

Prettier 2 fallback

The plugin needs Prettier 3, which introduced async preprocess. On Prettier 2 run the CLI before Prettier instead, in sequence:

package.json

{
    "lint-staged": {
        "*.{ts,tsx,js,jsx}": ["apotheke --write", "prettier --write"]
    }
}

Trying it without installing

Point Prettier at a built plugin file directly:

npx prettier@3 \
  --plugin /path/to/apotheke/dist/index.js \
  --write 'src/App.tsx'

Local development against a checkout

From an apotheke clone:

pnpm install && pnpm build
pnpm --filter apotheke exec pnpm link --global

Then in the target repo:

pnpm link --global apotheke

Re-run pnpm build in the apotheke checkout after each source change — the plugin loads dist/, not the TypeScript sources.