pomelo-scheduler
Advanced tools
Comparing version 0.3.8 to 0.3.9
@@ -71,5 +71,5 @@ /** | ||
} | ||
date.setDate(1); | ||
date.setMonth(nextMonth); | ||
date.setDate(1); | ||
date.setHours(0); | ||
@@ -90,4 +90,4 @@ date.setMinutes(0); | ||
if(nextDom <= date.getDate() || nextDom > domLimit){ | ||
date.setDate(1); | ||
date.setMonth(date.getMonth() + 1); | ||
date.setDate(1); | ||
date.setHours(0); | ||
@@ -94,0 +94,0 @@ date.setMinutes(0); |
{ | ||
"name": "pomelo-scheduler", | ||
"version": "0.3.8", | ||
"version": "0.3.9", | ||
"main": "./lib/schedule", | ||
"author": "XiaogangZhang <zhang0925@gmail.com>", | ||
"dependencies": { | ||
"log4js" : ">=0.4.1" | ||
"log4js" : "0.6.7" | ||
} | ||
} |
@@ -107,3 +107,3 @@ # pomelo-scheduler | ||
//Add a simple job and save the id | ||
var id = schedule.scheduleJob({period: 1000}, cronJob, {); | ||
var id = schedule.scheduleJob({period: 1000}, simpleJob, {}); | ||
@@ -110,0 +110,0 @@ /** |
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
33036
1
+ Addedasync@0.1.15(transitive)
+ Addedcore-util-is@1.0.3(transitive)
+ Addeddequeue@1.0.3(transitive)
+ Addedinherits@2.0.4(transitive)
+ Addedisarray@0.0.1(transitive)
+ Addedlog4js@0.6.7(transitive)
+ Addedreadable-stream@1.0.34(transitive)
+ Addedsemver@1.1.4(transitive)
+ Addedstring_decoder@0.10.31(transitive)
- Removeddate-format@4.0.14(transitive)
- Removeddebug@4.4.0(transitive)
- Removedflatted@3.3.2(transitive)
- Removedfs-extra@8.1.0(transitive)
- Removedgraceful-fs@4.2.11(transitive)
- Removedjsonfile@4.0.0(transitive)
- Removedlog4js@6.9.1(transitive)
- Removedms@2.1.3(transitive)
- Removedrfdc@1.4.1(transitive)
- Removedstreamroller@3.1.5(transitive)
- Removeduniversalify@0.1.2(transitive)
Updatedlog4js@0.6.7