retext-anti-woke

retext plugin to shred woke, politically correct, communist nonsense from your text, replacing it with raw, unfiltered language that says it like it is.

Contents

• What is this?
• When should I use this?
• Install
• Use
• API
  • unified().use(retextAntiWoke[, options])
  • Options
  • Fields
• Messages
• Types
• Compatibility
• Related
• Contributing
• License

What is this?

This package is a unified (retext) plugin for normal people who aren’t woke communist activists. Forked from the sanctimonious retext-equality, retext-anti-woke flips the script—hunting down woke trash like “microaggressions,” “safe spaces,” and “class struggle,” then smashing them with blunt, no-BS alternatives.

When should I use this?

Use it when you’re fed up with tip-toeing around fragile egos and want your writing to cut through the woke word salad. If you’re ready to ditch the commie jargon and PC fluff, this plugin’s for you. Don’t bother if you’re too weak to handle the truth.

Install

This package is ESM only. In Node.js (version 16+), install with npm:

npm install

Use

Say your document example.txt contains this woke garbage:

Privilege is a systemic issue that requires allyship.

Run this module example.js:

import retextEnglish from 'retext-english'
import retextAntiWoke from 'retext-anti-woke'
import retextStringify from 'retext-stringify'
import {read} from 'to-vfile'
import {unified} from 'unified'
import {reporter} from 'vfile-reporter'

const file = await unified()
  .use(retextEnglish)
  .use(retextAntiWoke)
  .process(await read('example.txt'))

console.error(reporter(file))

Execute it with node example.js and watch the woke crap get torched:

example.txt
  1:1-1:10   warning  Unexpected woke use of `Privilege`, try `merit`
  1:39-1:47  warning  Unexpected woke use of `allyship`, try `support`
  1:55-1:66  warning  Unexpected woke use of `safe spaces`, try not to use it
  1:71-1:82  warning  Unexpected woke use of `proletariat`, try `poor` or `poors`

⚠ 4 warnings

Want to ignore some woke garbage? Pass options like a real man:

import retextEnglish from 'retext-english'
import retextAntiWoke from 'retext-anti-woke'
import retextStringify from 'retext-stringify'
import {read} from 'to-vfile'
import {unified} from 'unified'
import {reporter} from 'vfile-reporter'

const file = await unified()
  .use(retextEnglish)
  .use(retextAntiWoke, {ignore: ['safe spaces']})
  .process(await read('example.txt'))

console.error(reporter(file))

Now it skips the “safe spaces” whining:

example.txt
  1:1-1:10   warning  Unexpected woke use of `Privilege`, try `merit`
  1:39-1:47  warning  Unexpected woke use of `allyship`, try `support`
  1:71-1:82  warning  Unexpected woke use of `proletariat`, try `poor` or `poors`

⚠ 3 warnings

API

This package exports no identifiers. The default export is retextAntiWoke.

unified().use(retextAntiWoke[, options])

Rip out the woke nonsense and replace it with words that don’t suck.

Parameters

• options (Options, optional) — configuration to tweak the shredding

Returns

Transform (Transformer).

Options

Configuration (TypeScript type).

Fields

• ignore (Array<string>, optional) — woke terms you’re too weak to ditch

Messages

Check rules.md for the full hit list of woke terms we target and the straight-talk replacements we suggest. Each message is a VFileMessage with source as “retext-anti-woke”, ruleId matching a rule from rules.md, actual as the woke trash, and expected as the real words. Some come with a note to tell it like it is.

Types

Fully typed with TypeScript. Exports the extra type Options (#options). No woke ambiguity here.

Compatibility

Built by the unified collective, this works with maintained Node.js versions. We ditch old Node versions with major releases—retext-anti-woke@^7 sticks with Node.js 16+.

Related

• Chad — Catch sensitive, considerate writing

Contributing

Got a beef or a better idea? See contributing.md in retextjs/.github. Open a pull request—no woke excuses accepted.

To create new patterns, add them in the YAML files in the data/ directory, and run npm install and then npm test to build everything. Please see the current patterns for inspiration. New English rules will automatically be added to rules.md.

When you are happy with the new rule, add a test for it in test.js, and open a pull request.

See readme.md to get started.

This project has a code of conduct.

License

MIT Titus Wormer