1.3.0 breaks on install

I have prism-react-renderer as dependency of my Docusaurus project and upon upgrading this package it breaks at yarn install:

error /app/node_modules/prism-react-renderer: Command failed.
Exit code: 127
Command: patch-package
Arguments:
Directory: /app/node_modules/prism-react-renderer
Output:
/bin/sh: patch-package: not found

[jpdriver]

my sincerest apologies to all who ran into this today. way to go for my first release of this lib huh 😅

after further investigation (h/t to @ryan-roemer for the info above) the simplest solution was to move the patch-package invocation to a prebuild script.

when you think about it, this is actually when we want to modify prism so we can vendor it anyway. when a consuming project installs prism-react-renderer there’s no need to repeat the modification.

this solution avoids both needing to add dependencies and also avoids shipping the /patches dir as part of our archive.

[xenoworf]

My team is seeing a similar error when installing via npm install:

> prism-react-renderer@1.3.0 postinstall /Users/me/my-project/node_modules/prism-react-renderer
> patch-package

sh: patch-package: command not found
npm WARN @cerner/package-json-lint-config-terra@1.2.0 requires a peer of @cerner/package-json-lint@^0.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @octokit/plugin-request-log@1.0.4 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-plugin-formatjs@2.21.0 requires a peer of eslint@8 but none is installed. You must install peer dependencies yourself.

npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! prism-react-renderer@1.3.0 postinstall: `patch-package`
npm ERR! spawn ENOENT