electron/atom/common/api/lib/original-fs.coffee

vm = require 'vm'

# Execute the 'fs.js' and pass the 'exports' to it.
source = '(function (exports, require, module, __filename, __dirname) { ' +
         process.binding('natives').originalFs +
         '\n});'
fn = vm.runInThisContext source, { filename: 'fs.js' }
fn exports, require, module
Evaluate the "fs.js" in original-fs Some high-level APIs in fs are using low-level APIs via "fs.xxx", which will be overriden by our asar wrappers, so just shadow-copy those methods is not enough. By evaluating the whole "fs.js" we can make sure original-fs is not polluted by the asar wrappers. Fixes #782. 2015-01-19 14:22:32 -08:00			`vm = require 'vm'`
Add original-fs module 2014-11-12 11:09:59 +08:00
Evaluate the "fs.js" in original-fs Some high-level APIs in fs are using low-level APIs via "fs.xxx", which will be overriden by our asar wrappers, so just shadow-copy those methods is not enough. By evaluating the whole "fs.js" we can make sure original-fs is not polluted by the asar wrappers. Fixes #782. 2015-01-19 14:22:32 -08:00			`# Execute the 'fs.js' and pass the 'exports' to it.`
			`source = '(function (exports, require, module, __filename, __dirname) { ' +`
Redirect process.binding('natives').fs to global fs object 2015-01-31 23:47:47 -08:00			`process.binding('natives').originalFs +`
Evaluate the "fs.js" in original-fs Some high-level APIs in fs are using low-level APIs via "fs.xxx", which will be overriden by our asar wrappers, so just shadow-copy those methods is not enough. By evaluating the whole "fs.js" we can make sure original-fs is not polluted by the asar wrappers. Fixes #782. 2015-01-19 14:22:32 -08:00			`'\n});'`
			`fn = vm.runInThisContext source, { filename: 'fs.js' }`
			`fn exports, require, module`