cron - npm Package Compare versions

cron

Package Overview

Dependencies

Maintainers

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

Comparing version 2.4.3 to 2.4.4

CHANGELOG.md

		@@ -0,1 +1,8 @@
		## [2.4.4](https://github.com/kelektiv/node-cron/compare/v2.4.3...v2.4.4) (2023-09-25)


		### 🐛 Bug Fixes

		* added fractional offset support ([#685](https://github.com/kelektiv/node-cron/issues/685)) ([ce78478](https://github.com/kelektiv/node-cron/commit/ce784784575b65bd75b8b1a4adda3d8fd42fe1c0))

		## [2.4.3](https://github.com/kelektiv/node-cron/compare/v2.4.2...v2.4.3) (2023-08-26)
		@@ -2,0 +9,0 @@

lib/time.js

		@@ -155,13 +155,22 @@ const CONSTRAINTS = [
		if (typeof this.utcOffset !== 'undefined') {
		let offset =
		const offsetHours = parseInt(
		this.utcOffset >= 60 \|\| this.utcOffset <= -60
		? this.utcOffset / 60
		: this.utcOffset;
		offset = parseInt(offset);
		: this.utcOffset
		);

		const offsetMins =
		this.utcOffset >= 60 \|\| this.utcOffset <= -60
		? Math.abs(this.utcOffset - offsetHours * 60)
		: 0;
		const offsetMinsStr = offsetMins >= 10 ? offsetMins : '0' + offsetMins;

		let utcZone = 'UTC';
		if (offset < 0) {
		utcZone += offset;
		} else if (offset > 0) {
		utcZone += `+${offset}`;

		if (parseInt(this.utcOffset) < 0) {
		utcZone += `${
		offsetHours === 0 ? '-0' : offsetHours
		}:${offsetMinsStr}`;
		} else {
		utcZone += `+${offsetHours}:${offsetMinsStr}`;
		}
		@@ -168,0 +177,0 @@

package.json

		{
		"name": "cron",
		"description": "Cron jobs for your node",
		"version": "2.4.3",
		"version": "2.4.4",
		"author": "Nick Campbell <nicholas.j.campbell@gmail.com> (https://github.com/ncb000gt)",
		@@ -6,0 +6,0 @@ "bugs": {

README.md

		@@ -97,6 +97,6 @@ <p align="center">
		- `start` - [OPTIONAL] - Specifies whether to start the job just before exiting the constructor. By default this is set to false. If left at default you will need to call `job.start()` in order to start the job (assuming `job` is the variable you set the cronjob to). This does not immediately fire your `onTick` function, it just gives you more control over the behavior of your jobs.
		- `timeZone` - [OPTIONAL] - Specify the time zone for the execution. This will modify the actual time relative to your time zone. If the time zone is invalid, an error is thrown. By default (if this is omitted) the local time zone will be used. You can check all time zones available at [Moment Timezone Website](http://momentjs.com/timezone/). Probably don't use both `timeZone` and `utcOffset` together or weird things may happen.
		- `timeZone` - [OPTIONAL] - Specify the time zone for the execution. This will modify the actual time relative to your time zone. If the time zone is invalid, an error is thrown. By default (if this is omitted) the local time zone will be used. You can check the various time zones format accepted in the [Luxon documentation](https://github.com/moment/luxon/blob/master/docs/zones.md#specifying-a-zone). Note: This parameter supports minutes offsets, e.g. `UTC+5:30`. Warning: Probably don't use both `timeZone` and `utcOffset` together or weird things may happen.
		- `context` - [OPTIONAL] - The context within which to execute the onTick method. This defaults to the cronjob itself allowing you to call `this.stop()`. However, if you change this you'll have access to the functions and values within your context object.
		- `runOnInit` - [OPTIONAL] - This will immediately fire your `onTick` function as soon as the requisite initialization has happened. This option is set to `false` by default for backwards compatibility.
		- `utcOffset` - [OPTIONAL] - This allows you to specify the offset of your time zone rather than using the `timeZone` param. This should be an integer amount representing the number of minutes offset (like `120` for +2 hours or `-90` for -1.5 hours) Probably don't use both `timeZone` and `utcOffset` together or weird things may happen.
		- `utcOffset` - [OPTIONAL] - This allows you to specify the offset of your time zone rather than using the `timeZone` param. This should be an integer representing the number of minutes offset (like `120` for +2 hours or `-90` for -1.5 hours). Warning: Minutes offsets < 60 and >-60 will be treated as an offset in hours. This means a minute offset of `30` means an offset of +30 hours. Use the `timeZone` param in this case. This behavior [is planned to be removed in V3](https://github.com/kelektiv/node-cron/pull/685#issuecomment-1676417917). Warning: Probably don't use both `timeZone` and `utcOffset` together or weird things may happen.
		- `unrefTimeout` - [OPTIONAL] - If you have code that keeps the event loop running and want to stop the node process when that finishes regardless of the state of your cronjob, you can do so making use of this parameter. This is off by default and cron will run as if it needs to control the event loop. For more information take a look at [timers#timers_timeout_unref](https://nodejs.org/api/timers.html#timers_timeout_unref) from the NodeJS docs.
		@@ -103,0 +103,0 @@ - `start` - Runs your job.

Improved metrics