structure, layout and automation

This commit is contained in:
Tancre
2020-09-16 14:23:28 +02:00
commit 0efda7fffe
15549 changed files with 1280031 additions and 0 deletions

31
node_modules/node-sass/scripts/util/downloadoptions.js generated vendored Normal file
View File

@ -0,0 +1,31 @@
var proxy = require('./proxy'),
userAgent = require('./useragent');
/**
* The options passed to request when downloading the bibary
*
* There some nuance to how request handles options. Specifically
* we've been caught by their usage of `hasOwnProperty` rather than
* falsey checks. By moving the options generation into a util helper
* we can test for regressions.
*
* @return {Object} an options object for request
* @api private
*/
module.exports = function() {
var options = {
rejectUnauthorized: false,
timeout: 60000,
headers: {
'User-Agent': userAgent(),
},
encoding: null,
};
var proxyConfig = proxy();
if (proxyConfig) {
options.proxy = proxyConfig;
}
return options;
};

22
node_modules/node-sass/scripts/util/proxy.js generated vendored Normal file
View File

@ -0,0 +1,22 @@
/**
* Determine the proxy settings configured by npm
*
* It's possible to configure npm to use a proxy different
* from the system defined proxy. This can be done via the
* `npm config` CLI or the `.npmrc` config file.
*
* If a proxy has been configured in this way we must
* tell request explicitly to use it.
*
* Otherwise we can trust request to the right thing.
*
* @return {String} the proxy configured by npm or an empty string
* @api private
*/
module.exports = function() {
return process.env.npm_config_https_proxy ||
process.env.npm_config_proxy ||
process.env.npm_config_http_proxy ||
'';
};

13
node_modules/node-sass/scripts/util/useragent.js generated vendored Normal file
View File

@ -0,0 +1,13 @@
var pkg = require('../../package.json');
/**
* A custom user agent use for binary downloads.
*
* @api private
*/
module.exports = function() {
return [
'node/', process.version, ' ',
'node-sass-installer/', pkg.version
].join('');
};