Scott Sadler

@shinokada > What is ! at the end of justify! and buttonType!? That is TypeScript's [non-null assertion operator](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-0.html#non-null-assertion-operator).

Because of the "missing" named export, you can't use `styled-components` with the upcoming TypeScript 4.7 `nodenext` resolution mode. https://github.com/microsoft/TypeScript/issues/49189

Also appears to be incompatible with [prettier-plugin-jsdoc](https://www.npmjs.com/package/prettier-plugin-jsdoc). My prettier config: ``` { "$schema": "http://json.schemastore.org/prettierrc", "endOfLine": "lf", "jsxSingleQuote": true, "printWidth": 100, "quoteProps": "consistent", "singleQuote": true, "trailingComma": "none", "useTabs": false, "overrides": [...

To expound on this report, the specific error I am seeing that was introduced in version `2.1.7` is: ``` error TS7031: Binding element '$xxx' implicitly has an 'any' type. ```...

@Roseidon - The way I worked around this was to disable the `jsdoc/require-description-complete-sentence` rule entirely and, instead, configure the `jsdoc/match-description` rule to require a complete sentence. ```javascript 'jsdoc/match-description': [ 'error',...

Just ran into this issue today. Anything I can do to help get the PR merged?

@Vasile-Peste - The [link](https://www.npmjs.com/package/link) package along with a `prepare` hook has been an excellent alternative for me. > npx link = A safer version of `npm link`. ```json { "scripts":...