Releases: eps1lon/types-react-codemod
v3.5.0
Minor Changes
-
Run
no-implicit-ref-callback-return
andreact-element-default-any
by default inpreset-19
(#43310085c8
by @eps1lon)The transformed code is not meant to be used as a pattern for new code.
It really is about migrating existing code with as little friction.
Changes can always be reverted and a subset chosen.
v3.4.1
v3.4.0
v3.3.0
Minor Changes
-
Add
react-element-default-any-props
codemod (#3714191845
by @eps1lon)Opt-in codemod in
preset-19
.// implies `React.ReactElement<unknown>` in React 19 as opposed to `React.ReactElement<any>` in prior versions. -declare const element: React.ReactElement +declare const element: React.ReactElement<any>
Only meant to migrate old code not a recommendation for how to type React elements.
v3.2.0
Minor Changes
-
Add
no-implicit-ref-callback-return
transform (#3697535bfc
by @eps1lon)Ensures you don't accidentally return anything from ref callbacks since the return value was always ignored.
With ref cleanups, this is no longer the case and flagged in types to avoid mistakes.-<div ref={current => (instance = current)} /> +<div ref={current => {instance = current}} />
The transform is opt-in in the
preset-19
in case you already used ref cleanups in Canary releases.
v3.1.1
v3.1.0
Minor Changes
-
Add codemod to replace deprecated
ReactFragment
by inlining its actual type (#326ed97a70
by @eps1lon)import * as React from 'react'; -const node: React.ReactFragment +const node: Iterable<React.ReactNode>
-
Add codemod to replace deprecated React types related to propTypes with their counterpart from the
prop-types
package (#3571751318
by @eps1lon)+import * as PropTypes from "prop-types"; import * as React from "react"; -declare const requireable: React.Requireable<React.ReactNode>; +declare const requireable: PropTypes.Requireable<React.ReactNode>; -declare const validator: React.Validator<React.ReactNode>; +declare const requireable: PropTypes.Validator<React.ReactNode>; -declare const validationMap: React.ValidationMap<{}>; +declare const requireable: PropTypes.ValidationMap<React.ReactNode>; -declare const weakValidationMap: React.WeakValidationMap<{}>; +declare const requireable: PropTypes.WeakValidationMap<React.ReactNode>;
-
Add codemod for required initial value in
useRef
(#2170047404
by @eps1lon)Added as
useRef-required-initial
.
Can be used on 18.x types but only intended for once DefinitelyTyped/DefinitelyTyped#64920 lands. -
Unflag codemods for new refs (#319
80fe29c
by @eps1lon)Just removing their experimental prefix since we have increased confidence in these changes after seeing their impact internally.
-experimental-refobject-defaults +refobject-defaults
-
Add codemod to replace
LegacyRef
withRef
(#347e928761
by @eps1lon) -
Add codemod to replace deprecated
ReactNodeArray
by inlining its actual type. (#325b7f757c
by @eps1lon)import * as React from 'react'; -const node: React.ReactNodeArray +const node: ReadonlyArray<React.ReactNode>
Patch Changes
-
Added missing transforms as choices to preset-19 (#341
dc10a3d
by @eps1lon) -
Ensure added imports of types use the
type
modifier (#343f05624f
by @eps1lon)If we'd previously add an import to
JSX
(e.g. inscoped-jsx
),
the codemod would import it as a value.
This breaks TypeScript projects usingverbatimModuleSyntax
as well as projects enforcingtype
imports for types.Now we ensure new imports of types use the
type
modifier:-import { JSX } from 'react' +import { type JSX } from 'react'
This also changes how we transform the deprecated global JSX namespace.
Instead of rewriting each usage, we opt for adding another import.
The guiding principle being that we keep the changes minimal in a codemod.Before:
import * as React from 'react' -const element: JSX.Element +const element: React.JSX.Element
After:
import * as React from 'react' +import { type JSX } from 'react' const element: JSX.Element
Note that rewriting of imports does not change the modifier.
For example, thedeprecated-vfc-codemod
rewritesVFC
identifiers toFC
.
If the import ofVFC
had notype
modifier, the codemod will not add one.type
modifiers for import specifiers require [TypeScript 4.5 which has reached EOL](https://github.com/DefinitelyTyped/DefinitelyTyped#support-window in DefinitelyTyped) which is a strong signal that you should upgrade to at least TypeScript 4.6 by now. -
Ensure replace and rename codemods have consistent behavior (#348
a62832e
by @eps1lon)Fixes multiple incorrect transform patterns that were supported by some transforms but not others.
We no longer switch totype
imports if the original type wasn't imported with that modifier.
Type parameters are now consistently preserved.
We don't add a reference to theReact
namespace anymore if we can just add a type import.This affects the following codemods:
deprecated-legacy-ref
deprecated-react-child
deprecated-react-text
deprecated-react-type
deprecated-sfc-element
deprecated-sfc
deprecated-stateless-component
deprecated-void-function-component
-
Find and replace type usage in type parameters of call expressions (#344
8c27551
by @eps1lon)Now we properly detect that e.g.
JSX
is used insomeFunctionWithTypeParameters<JSX>()
.Affected codemods:
deprecated-react-child
deprecated-react-text
scoped-jsx
v3.0.0
Major Changes
-
#304
0730d90553bd7dfc889a1325c9e975c16f367439
Thanks @renovate! - Update Node.js support matrixDrop support for unmaintained Node.js versions (14.x, 16.x, 17.x, and 19.x) to reduce maintenance cost.
Minor Changes
-
#214
10fb254afbccab5e7e1941bfee49f957ca7ed1a5
Thanks @eps1lon! - Add scoped-jsx transformThis replaces usage of the deprecated global JSX namespace with usage of the scoped namespace:
+import { JSX } from 'react' const element: JSX.Element