From 6f937de84409fe0d0ea2edda2ec372145fc68d0f Mon Sep 17 00:00:00 2001 From: Anton Gilgur Date: Mon, 7 Sep 2020 15:08:22 -0400 Subject: [PATCH] docs: add `patch-package` reference to Customization section - it was first recommended by Shawn in issues then strongly recommended by Jared and I've recommended it a few times too for smaller changes - Quoting Jared: "Yes, to documenting patch-package as ultimate escape hatch" --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index fd37ff40d..514b62b35 100644 --- a/README.md +++ b/README.md @@ -30,6 +30,7 @@ Despite all the recent hype, setting up a new TypeScript (x React) library can b - [Babel](#babel) - [Jest](#jest) - [ESLint](#eslint) + - [`patch-package`](#patch-package) - [Inspiration](#inspiration) - [Comparison with Microbundle](#comparison-with-microbundle) - [API Reference](#api-reference) @@ -387,6 +388,11 @@ You can add your own `jest.config.js` to the root of your project and TSDX will You can add your own `.eslintrc.js` to the root of your project and TSDX will **deep merge** it with [its own ESLint config](./src/createEslintConfig.ts). +### `patch-package` + +If you still need more customizations, we recommend using [`patch-package`](https://github.com/ds300/patch-package) so you don't need to fork. +Keep in mind that these types of changes may be quite fragile against version updates. + ## Inspiration TSDX was originally ripped out of [Formik's](https://github.com/jaredpalmer/formik) build tooling.