sourcemap-validator - npm Package Compare versions

Comparing version 1.0.4 to 1.0.5

index.js

@@ -26,12 +26,14 @@ var validate
 validateMapping = function (mapping) {
-  assert.ok(mapping.generatedColumn!=null, 'missing generated column');
-  assert.ok(mapping.generatedLine!=null, 'missing generated line');
-  assert.ok(mapping.generatedColumn >= 0, 'generated column must be greater or equal to zero');
-  assert.ok(mapping.generatedLine >= 0, 'generated line must be greater or equal to zero');
+  var prettyMapping = JSON.stringify(mapping, null, 2);
 
-  assert.ok(mapping.originalColumn!=null, 'missing original column');
-  assert.ok(mapping.originalLine!=null, 'missing original line');
-  assert.ok(mapping.originalColumn >= 0, 'original column must be greater or equal to zero');
-  assert.ok(mapping.originalLine >= 0, 'original line must be greater or equal to zero');
+  assert.ok(mapping.generatedColumn!=null, 'missing generated column, mapping: ' + prettyMapping);
+  assert.ok(mapping.generatedLine!=null, 'missing generated line, mapping: ' + prettyMapping);
+  assert.ok(mapping.generatedColumn >= 0, 'generated column must be greater or equal to zero, mapping: ' + prettyMapping);
+  assert.ok(mapping.generatedLine >= 0, 'generated line must be greater or equal to zero: ' + prettyMapping);
 
+  assert.ok(mapping.originalColumn!=null, 'missing original column, mapping: ' + prettyMapping);
+  assert.ok(mapping.originalLine!=null, 'missing original line, mapping: ' + prettyMapping);
+  assert.ok(mapping.originalColumn >= 0, 'original column must be greater or equal to zero, mapping: ' + prettyMapping);
+  assert.ok(mapping.originalLine >= 0, 'original line must be greater or equal to zero, mapping: ' + prettyMapping);
+
   assert.notEqual(mapping.source, null, 'source is missing');
@@ -38,0 +40,0 @@ };

package.json

@@ -21,3 +21,3 @@ {
   ],
-  "version": "1.0.4",
+  "version": "1.0.5",
   "repository": {
@@ -24,0 +24,0 @@ "type": "git",

New alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

New author

Supply chain risk

A 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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Minified code

Quality

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

Found 2 instances in 1 package

Fixed alerts

No README

Quality

Package does not have a README. This may indicate a failed publish or a low quality package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1311177

increased by22549.46%

Number of package files

21

increased by600%

Lines of code

27156

increased by21800%

Number of medium quality alerts

0

decreased by-100%

Number of lines in readme file

91

increased byInfinity%

Worsened metrics

Number of low quality alerts

3

increased by200%

Number of low supply chain risk alerts

4

increased byInfinity%

Number of medium supply chain risk alerts

2

increased byInfinity%

No dependency changes