Comparing version 0.1.0 to 0.1.1
@@ -8,4 +8,8 @@ var sander = require( 'sander' ), | ||
return node.init().then( function () { | ||
if ( node.isOriginalSource ) { | ||
return null; | ||
} | ||
return node.build( options ); | ||
}); | ||
}; |
{ | ||
"name": "sorcery", | ||
"description": "Resolve a chain of sourcemaps back to the original source", | ||
"version": "0.1.0", | ||
"version": "0.1.1", | ||
"author": "Rich Harris", | ||
"repository": "https://github.com/Rich-Harris/sorcery", | ||
"main": "lib/index.js", | ||
"license": "MIT", | ||
"dependencies": { | ||
"sander": "^0.1.5", | ||
"sander": "^0.1.6", | ||
"vlq": "^0.1.0" | ||
@@ -10,0 +12,0 @@ }, |
# sorcery.js | ||
Sourcemaps are great - if you have a JavaScript file, and you minify it, your minifier can generate a mapping back that lets you debug as though you were looking at the original uncompressed code. | ||
Sourcemaps are great - if you have a JavaScript file, and you minify it, your minifier can generate a map that lets you debug as though you were looking at the original uncompressed code. | ||
@@ -5,0 +5,0 @@ But if you have more than one transformation - say you want to transpile your JavaScript, concatenate several files into one, and minify the result - it gets a little trickier. Each intermediate step needs to be able to both *ingest* a sourcemap and *generate* one, all the time pointing back to the original source. |
@@ -21,3 +21,5 @@ var sorcery = require( '../../' ), | ||
.catch( function ( err ) { | ||
console.log( 'err', err ); | ||
setTimeout( function () { | ||
throw err; | ||
}); | ||
}); | ||
@@ -24,0 +26,0 @@ |
@@ -6,3 +6,3 @@ (function() { | ||
console.log('the answer is ' + answer); | ||
console.log("the answer is " + answer); | ||
@@ -9,0 +9,0 @@ }).call(this); |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
13187
23
311
1
Updatedsander@^0.1.6