@attestate/crawler
Advanced tools
Changelog
0.6.1
Changelog
0.6.0
config.environment
(including overwritten environment variables) is now
passed into extractor.{init|update}
. We stop recommend using process.env
in strategies.coordinator.remote
the input is now an object remote({environment, execute})
. Here, we also stop recommend using process.env
directly.config.environment
did NOT take presedence over its process.env
counter-part. It does now.Changelog
0.5.3
path[0].coordinator.archive: Boolean
that allows to delete
extraction and transformation files after a single coordinator run.Changelog
0.5.1
function lifecycle.load()
now exits gracefully when prior transform job has
no processable outputs.Changelog
0.5.0
config.path[]
for transformer, extractor and loader, the
properties output.path
and input.path
were renamed to output.name
and
doesn't have to be a path anymore. Instead, they are file names that are
automatically resolved from within env.DATA_DIR
.process.env
variables defined in the .env
file can now also be
defined (and overwritten) in the config.mjs
file's environment
property.function init({ state, args, execute })
function update({ message })
function onLine({ state })
where state.line
is the line
function. args
can be matched too.function* order({ state })
where state.line
is the linefunction* direct({ state })
where state.line
is the linepath
property) features a new
field called coordinator
where a module
and an interval
can be defined.
They're used to re-run the first path once all jobs have been completed, to
e.g. keep in synchronization with a network like Ethereum.@attestate/crawler-call-block-logs
module at version 0.3.0 is
compatible.Changelog
0.4.0
crawler.mjs range
commandChangelog
0.3.0
loader.handler
to two generator functions order
and
direct
as a property called module
(consistent with extractor and
transformer)configuration.output.path
object is now requiredconfiguration.loader.module
object is now requiredChangelog
0.2.0
EXTRACTION_WORKER_CONCURRENCY
into configuration file