-
Add
react-element-default-any-propscodemod (#3714191845by @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.
-
Add
no-implicit-ref-callback-returntransform (#3697535bfcby @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-19in case you already used ref cleanups in Canary releases.
-
Add codemod to replace deprecated
ReactFragmentby inlining its actual type (#326ed97a70by @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-typespackage (#3571751318by @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(#2170047404by @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
80fe29cby @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
LegacyRefwithRef(#347e928761by @eps1lon) -
Add codemod to replace deprecated
ReactNodeArrayby inlining its actual type. (#325b7f757cby @eps1lon)import * as React from 'react'; -const node: React.ReactNodeArray +const node: ReadonlyArray<React.ReactNode>
-
Added missing transforms as choices to preset-19 (#341
dc10a3dby @eps1lon) -
Ensure added imports of types use the
typemodifier (#343f05624fby @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 usingverbatimModuleSyntaxas well as projects enforcingtypeimports for types.Now we ensure new imports of types use the
typemodifier:-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.ElementNote that rewriting of imports does not change the modifier. For example, the
deprecated-vfc-codemodrewritesVFCidentifiers toFC. If the import ofVFChad notypemodifier, the codemod will not add one.typemodifiers 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
a62832eby @eps1lon)Fixes multiple incorrect transform patterns that were supported by some transforms but not others. We no longer switch to
typeimports if the original type wasn't imported with that modifier. Type parameters are now consistently preserved. We don't add a reference to theReactnamespace anymore if we can just add a type import.This affects the following codemods:
deprecated-legacy-refdeprecated-react-childdeprecated-react-textdeprecated-react-typedeprecated-sfc-elementdeprecated-sfcdeprecated-stateless-componentdeprecated-void-function-component
-
Find and replace type usage in type parameters of call expressions (#344
8c27551by @eps1lon)Now we properly detect that e.g.
JSXis used insomeFunctionWithTypeParameters<JSX>().Affected codemods:
deprecated-react-childdeprecated-react-textscoped-jsx
-
#304
0730d90553bd7dfc889a1325c9e975c16f367439Thanks @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.
-
#214
10fb254afbccab5e7e1941bfee49f957ca7ed1a5Thanks @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
-
#208
b76beabThanks @eps1lon! - Add experimental (not for use in published types)experimental-refobject-defaultscodemod for newRefObjectbehavior
- #248
0dd5d20Thanks @dgarciamuria! - Add missing@babel/parserdependency
-
#210
a47bd09Thanks @eps1lon! - Ensure jscodeshift can be executedFixes
/usr/bin/env: ‘node\r’: No such file or directory
-
#143
b3351d2Thanks @eps1lon! - Fail install if used version of Node.js is not officially supportedAdd a list of supported versions of Node.js to
enginesinpackage.json. If the current version does not match, installation will fail (by default in Yarn and in NPM only if theengine-strictconfig is enabled).This warning can be ignored either by setting
engine-stricttofalsein NPM (default) or add--ignore-enginestoyarn(e.g.yarn --ignore-engines).
-
#92
0d92140Thanks @eps1lon! - Ensure TypeScript instantiation expressions can be parsedInstantiation expressions were added in TypeScript 4.7.
-
#69
52da899Thanks @eps1lon! - Don't useimportstatement.Fixes errors like "SyntaxError: Cannot use import statement outside a module".
-
#63
15ec796Thanks @eps1lon! - Avoid transpiling transformsPreviously jscodeshift would transpile the transforms before using them. This was largely unnecessary and resulted in bugs to to usage of undeclared Babel dependencies.
-
#46
c0784a7Thanks @eps1lon! - Parse .ts files without JSX plugin.Otherwise code such as
(<RegExp>expected).test(object);
could not be parsed.
-
#33
59e5624Thanks @eps1lon! - Remove repository config files from release.These files are only relevant for development.
-
#40
e425cc9Thanks @eps1lon! - Remove test files from release.There's a charm to having these in the release but nobody reads them anyway. And for testing you need the dev setup which is probably not available if inside node_modules.