Minor Changes
-
#628
bc98aaf
Thanks @benjie! - Now published as pure ESM, but
worry not as unflagged require(ESM) is now enabled by default in
Node 20.19.0+,
Node 22.12.0+ and Node 24+ so
everything should continue to work as before. -
#628
bc98aaf
Thanks @benjie! - For consistency,cosmiconfig
is no longer supported for configuration; usegraphile.config.tsinstead.
(This release will throw errors if you're using cosmisconfig, in later
releases cosmiconfigs will not be detected.) -
#628
bc98aaf
Thanks @benjie! - TypeScript task files with
.tsand.mtsextensions are now recognized by default and loaded through
Node's native type stripping if possible. Only erasable, verbatim TypeScript
syntax is supported without a custom loader or precompilation..js,.cjs
and.mjsfiles are prioritised ahead of.tsand.mtsfiles. -
#628
bc98aaf
Thanks @benjie! - We now use theexports
option, meaning sub-path imports (require("graphile-worker/...")) are no
longer supported. If you need something not exported by default, raise an
issue. -
#628
bc98aaf
Thanks @benjie! - Since Node 20 is EOL, Node 22
is now the minimum supported version, per our
requirements documentation. -
#628
bc98aaf
Thanks @benjie! -LogLevelexport is now type
only - a string union rather than a TypeScript const enum. -
#628
bc98aaf
Thanks @benjie! -Runnergains
[Symbol.asyncDispose]()method, so you can
await using runner = await run(...)and the worker will be released when you
reach the end of the scope. (Primarily useful for tests.)
Patch Changes
-
#628
bc98aaf
Thanks @benjie! - Fix issue where enabling
localQueuecould cause jobs from the same named queue to run concurrently
(violating the serial execution guarantee for named queues): a single batch
fetch could lock multiple jobs belonging to one named queue. Batch fetches now
return at most one job per named queue
(#621). -
#628
bc98aaf
Thanks @benjie! - Maintenance work: upgrade to
latest TypeScript, Jest, eliminate ts-node, fix yargs, use erasable syntax
only for type-stripping support.