add contributor workaround (#5510)

docs/api/cypress-api/custom-commands.mdx

@@ -847,8 +847,7 @@ couple commands.
 
 Don't do things like:
 
-- **<Icon name="exclamation-triangle" color="red" />**
-  `cy.clickButton(selector)`
+- **<Icon name="exclamation-triangle" color="red" />** `cy.clickButton(selector)`
 - **<Icon name="exclamation-triangle" color="red" />** `.shouldBeVisible()`
 
 This first custom command is wrapping `cy.get(selector).click()`. Going down
@@ -897,6 +896,38 @@ IntelliSense to show helpful documentation. See the
 [`cypress-example-todomvc`](https://github.com/cypress-io/cypress-example-todomvc#cypress-intellisense)
 repository for a working example.
 
+#### 6. Create a function that adds the custom command
+
+Cypress [12.17.4](/guides/references/changelog#12-17-4) includes a Webpack upgrade (v4 to v5), which [tree shakes out](https://webpack.js.org/blog/2020-10-10-webpack-5-release/#inner-module-tree-shaking) any side-effects or files that _only_ include side-effects.
+
+If you are using TypeScript and have Webpack's `sideEffects:false` set in your package.json, custom Cypress commands will not be registered by the common pattern of writing the commands in one file and having them be run as a side effect of importing the file. For example:
+
+```typescript
+// cypress/support/commands.ts
+Cypress.Commands.add("login", (email, password) => { ... })
+```
+
+```typescript
+// cypress/support/e2e.ts
+import './commands'
+```
+
+To support `sideEffects:false`, you can wrap the Cypress commands in a function that will be imported by the support file.
+
+```typescript
+// cypress/support/commands.ts
+export function registerCommands(){
+  Cypress.Commands.add("login", (email, password) => { ... })
+}
+```
+
+```typescript
+// cypress/support/e2e.ts
+import { registerCommands } from './commands'
+
+registerCommands()
+```
+
 ## History
 
 | Version                                       | Changes                      |