NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3376 most downloaded on npm
JavaScript parser written in OCaml. Produces ESTree AST
Latest stable
0.339.0
Last release 15 days ago
07 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
440 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
Likely to cause new Flow errors:
Likely to cause new Flow errors:
addEventListener() with 'click' and 'dblclick' will pass a MouseEvent to the listener. This means you might need to update foo.addEventListener('click', (e) => bar()) to foo.addEventListener('click', (e: MouseEvent) => bar()).New Features:
Notable bug fixes:
Misc:
foo has the typed mixed, we now allow foo.bar if you check that foo is not null or undefined.Parser:
let statements, which never made it into the spec (thanks @andreypopp)Likely to cause new Flow errors:
Likely to cause new Flow errors:
{[key: string]: ValueType}) were previously covariant which proved to be a significant source of unsoundness. Dictionary types are now invariant by default in order to fall into consistency with other collection types. It is possible to opt in to explicit covariance with new syntax: {+[key: string]: ValueType}, but note that this is now enforced covariance -- which means the dictionary can no longer be written into (only read from). For mutable collections, consider using Map/Set/etc. Please see this blog post for more information on variance.type T = {+covariantProp: string}. Please see this blog post for more information on variance.type T = {covariantMethod(): string} is the same as type T = {+covariantMethod: () => string}. Please see this blog post for more information on variance.New features:
empty type annotation. This is the "bottom type" which is the type that has no possible values. This is mostly useful for asserting impossible types right now (see the commit description for more details).--quiet flag to suppress server-status information that would otherwise be printed to stderr.React.createElement. See the commit message for more details.for-await-of statements.Notable bug fixes:
get-def and autocomplete on specifiers in import statements now works properly and links in to where the specifier is exported in the other file.Generator.prototype.return now returns a possibly-unfinished IteratorResult object rather than a definitely-done iterator result. See #2589 for more details.munge_underscores config option is set to true.Misc:
yield expressions no longer evaluate to an optional type. This is unsound, but the inconvenience was so prevalent that we decided to relax the issue for now. See #2080 for more details.Parser breaking changes:
ExportNamedDeclaration and ExportDefaultDeclaration nodes from ESTree rather than the outdated ExportDeclaration node.export default class {} now correctly emits a ClassDeclaration rather than ClassExpression per this estree issue.ExportSpecifier property names from id -> local and name -> exported per the latest ESTree spec.ExportBatchSpecifier to a ExportNamespaceSpecifier node per the latest ESTree spec.SpreadElementPattern -> RestElement per the latest ESTree spec.ObjectPattern are now named Property and RestProperty per the latest ESTree spec.Super node now instead of an Identifier node per the latest ESTree spec.{ImportNamedSpecifier and ImportDefaultSpecifier nodes now use proper local and remote property names, per the latest ESTree spec.mixed type annotation is now represented with a special MixedTypeAnnotation node (same as Babylon has been for a while).NullTypeAnnotation annotation node is now called NullLiteralTypeAnnotation in order to match Babylon.Your coding agent can read these notes before it upgrades. Set up the MCP server →
Likely to cause new Flow errors:
Likely to cause new Flow errors:
mixed to numberNew features:
suppress_comment now defaults to matching // $FlowFixMe if there are no suppress_comments listed in a .flowconfigpackage.json file is changedPromise.all() (thanks @vkurchatkin!)Notable bug fixes:
Function.prototype and Object.prototypeflow get-def wouldn't hop to the location of a type coming through an import typeany-typed variable as a computed-property lookup results in the wrong property-value typethrows at the toplevel of a module[libs] with an extension not listed in module.file_exts, it would previously be silently ignoredimport * as on a declare module.exports: any; libdef would not result in a module with every possible named export"JSX attributes must only be assigned a non-empty expression" syntax errors sometimes point to the wrong lineget or set in object short notationx = { async 123() { await y; } }u regex flagMisc:
new.target--pretty flag to all commands that have a --json flagflow coverage when --json is passed (thanks @aackerman!)Parser breaking changes:
SwitchStatementguardedHandlers from TryStatementAssignmentPattern for function param defaults to match ESTreeRestElement for function rest params to match ESTreeExpressionStatementCallExpression and MemberExpressionLikely to cause new Flow errors:
Likely to cause new Flow errors:
obj has a property foo that Flow doesn't know about, Flow will now refine obj.foo to the type mixed. If you then try to use obj.foo in an unsafe way (like as a function), you might start seeing errors mentioning property `foo` of unknown type. The fix is to either fix the type of obj to include an optional property foo, or to rewrite code like obj.foo && obj.foo(x) to typeof obj.foo === "function" && obj.foo(x)Array.prototype.find to reflect the fact that it can return undefinedNew Features:
{| and |} instead of { and }. Where {x: string} contains at least the property x, {| x: string |} contains ONLY the property x..css, .jpg, .png, .gif, .eot, .svg, .ttf, .woff, .woff2, .mp4 and .webm files (this list is not configurable at the moment). We call them resource files. If you require a resource file, you get a string (except for .css files, for which you get an Object). You should still be able to use module.name_mapper to map a resource file to a mock, if you prefer.flow gen-flow-files, which consumes Flow code and outputs .flow files containing only the types exported. It's alpha-level and we're still iterating on it, so use at your own peril!Notable bug fixes:
any, then the types it exported were also given type anyflow coverage had a non-termination bug. This is now fixed.Misc:
Likely to cause new Flow errors:
Likely to cause new Flow errors:
+. This may surface template strings with variables that may not safely coerce to a string.any -- but now this must be explicit. This behavior is toggleable via experimental.strict_type_args=false, but this config option will be removed in a near-term future release. There is also a codemod to help you automatically update old code.New Features:
declare export within declare module bodies. When declare export is used, the module being declared is inferred as an ES module. This enables the ability to export both named and default exports using declare module.Notable bug fixes:
Misc:
@flow in all comments at the top of the file (rather than just the first). It's also possible to configure this using a new max_header_tokens .flowconfig option.flow coverage commandRestored a bunch of deprecated/experimental/browser-specific APIs to the builtin flowlib and made them optional
(@gabelevi mistakenly listed a few v0.26.0 changes as being in v0.25.0. The Changelog has been updated to reflect reality. Sorry!)
Likely to cause new Flow errors:
New Features:
**)flow ls command to list the files that Flow can see.Notable bug fixes:
/x/* 5 */y/ - that's no comment!Misc:
…annotations, and removing non-standard and deprecated features. If you're relying on these things, then you may have new errors.
Likely to cause new Flow errors:
@marudor made a tremendous effort to clean up the builtin flowlib definitions, adding missing things, fixing annotations, and removing non-standard and deprecated features. If you're relying on these things, then you may have new errors.
In the past, generic types could leave off the type arguments. Flow is moving towards making these required. Applying type arguments to a polymorphic type (e.g. Map<string, number>) is like calling a function. If writing my_function was the same thing as writing my_function(), it would be really difficult to pass functions as values. Similarly, by making type arguments required, it frees us up to do more with our polymorphic types. If you have a polymorphic type with default types, like type Foo<T = number>, you can now write Foo<> to apply 0 type arguments to the polymorphic type Foo.
To ease migration, v0.25.0 still allows you to omit type arguments by default. v0.27.0 will start enforcing that type arguments are always supplied. To enable this behavior in v0.25.0, you can add experimental.strict_type_args=true to the .flowconfig.
New Features:
declare module.exports: type; <-- this is the new syntax to declare the CommonJS export type. Previously, you had to write declare var exports: type;. This can be used in .flow files and in declare module declarations.Misc:
Fixed parsing of JSON files with duplicate object keys
Likely to cause new Flow errors:
Likely to cause new Flow errors:
extends React.Component<DefaultProps, Props, void> (previously it was extends React.Component<DefaultProps, Props, {}>)state: State;if (o.noSuchP === foo) { ... }). These kinds of checks will now cause a type error.New features:
div, span, etc) and specify which properties they have.interface Generator<+Yield,+Return,-Next> {...}. Still pending transpiler support though.string and union types with string equality now properly refines the types.export * as from @leebyron's Stage1 proposal. Babel support hereNotable bug fixes:
this typethisswitch statements with default case.Misc:
Initial support for ES6 import/export (with CommonJS interop)
x != undefined and x != null as the same refinementAlso watch for changes in include paths
Update the parser to work with the new esprima-fb & ast-types
Flow comments should be ready for use
** Flow comments should be ready for use **
Type casts and import type should be ready for use
** Type casts and import type should be ready for use **
Nothing published for this version
Nothing published for this version
Fix refinement of optional nullable types
[Issue #4] Typecheck .jsx files
Initial release
Initial release
Nothing published for this version
One column per quarter.