Npm

License

The MIT License (MIT)

Copyright (c) 2013-2015 James Shore

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

How It Works

Simplebuild’s magic is based on standardized, composable function signatures and a very small supporting library. There are three kinds of Simplebuild modules:

• Task modules do the heavy lifting of task automation. For example, the module uses JSHint to check files for errors. Task modules export functions that follow a standard format: .

• Mapper modules augment task modules in some way. For example, the module adds a header to each task. Mappers output task modules, so they can be added to a build script without requiring individual tasks to be changed. Multiple mapper modules may be chained together.

• Extension modules are like mapper modules, except that they don’t have any restrictions on their input or output. They’re most often used for compatibility with other coding styles or build tools. For example, turns Simplebuild tasks into promises, and loads Simplebuild modules into Grunt.

Formal Specification

: 1 — Experimental

The key words «MUST», «MUST NOT», «REQUIRED», «SHALL», «SHALL NOT», «SHOULD», «SHOULD NOT», «RECOMMENDED», «MAY», and «OPTIONAL» in this section are to be interpreted as described in RFC 2119.

Task Modules

Task modules export functions that follow a common format. A task module SHOULD have a name starting with «simplebuild-» but not «simplebuild-map-» or «simplebuild-ext-«. (For example, «simplebuild-yourmodule.js».) All functions exported by a task module MUST be task functions.

Task functions MUST NOT be named , , or use a name ending in . (These restrictions are case-sensitive.) Any other name is permitted. Each task function MUST conform to this signature:

(REQUIRED): Configuration information. Any type of variable may be used, but an object is recommended. If a task function has no configuration, this variable is still required, but may be ignored.

(REQUIRED): Callback function. Each task function MUST call succeed() with no parameters when it finishes successfully.

(REQUIRED): Callback function. Each task function MUST call fail() with a brief human-readable explanation when it fails. The explanation SHOULD be less than 50 characters.

Task Behavior

Task functions MUST NOT return values or throw exceptions. Instead, either the or callback MUST be called exactly once when the task is complete. The callback may be called synchronously or asynchronously.

Tasks that fail SHOULD provide a detailed explanation suitable for debugging the problem. If the explanation is too long to fit in the 50-character failure mesage, the task SHOULD write the details to before failing. (Note that calling is a convenient way of writing to .)

Tasks that succeed SHOULD NOT write to by default. They MAY write more if configured to do so with the parameter.

Tasks that are slow or long-running MAY provide minimalistic progress output (such as periods) but SHOULD NOT provide more detailed information by default. They MAY provide more if configured to do so with the parameter.

Tasks SHOULD NOT write to under any circumstances.

Mapper Modules

Mapper modules export a single function, , that transforms a Simplebuild module in some way. A mapper module SHOULD have a name starting with . (For example, .)

Mapper modules MUST export only one function, named . The function call itself SHOULD NOT have any side effects, but the functions returns may. Mapper modules SHOULD use the API call defined in the module to create the function.

The function MUST take a single parameter and return an object, as follows. These requirements are handled automatically by .

• When the parameter is an object with a single key named , it will be considered to be a mapper module. In this case, the function MUST return a mapper module. The returned module’s function MUST wrap the provided mapper module so that calling is equivalent to calling

• When the parameter is any other object, it will be considered to be a task module. In this case, the function MUST return a task module. The returned task module SHOULD have different functions and/or behavior than the provided task module.

• When the parameter is a string, it will be considered to be an Node.js module. In this case, the function MUST use the Node.js API call to load the module, then apply the above rules.

Extension Modules

Extension modules extend the capabilities of Simplebuild. An extension module SHOULD have a name starting with «simplebuild-ext-» (for example, «simplebuild-ext-yourextension.js»).

Extension modules are unrestricted. They may export any number of functions, with any signatures, that do anything. When a function supports loading task modules by name, it SHOULD also support mapper modules as well. The API call defined in the module may be helpful here.

API

In addition to the Simplebuild spec, this npm module is also a library for use by Simplebuild module authors.

Task module authors may wish to use these functions:

• : Check the parameter provided to a simplebuild task.
• : Convert file globs into files.

Mapper and extension module authors may wish to use these functions:

• : Create the function required for a mapper module.
• : Modify every function in a module.

Applies defaults to a simplebuild task’s argument and type-checks the result.

• : The options passed into the task function. Must be an object.

• : The task’s default options. Any parameter that’s present in but not in will be included in the final options object.

• : An object containing the expected types for each option. The parameters in this object correspond to the parameters in the options object. The types are checked on the final options object after the defaults are applied. Any fields that are in the final options and not in the object will not be checked.

  • To specify a language type, use the corresponding object constructor: , , , , , or . For example, if your options include a «name» parameter that’s a string, you would use .

  • To specify an object type, use the object constructor, such as or . You may also pass in the constructor for a custom subclass. For example, if your options object requires a «timestamp» parameter that’s a Date object, you would use .

  • To specify specific object fields, recursively provide another -style object containing the fields you want to check. For example, if your options object requires a «report» object that contains a «verbose» boolean and a «filename» string, you would use .

  • To specify multiple valid types, provide an array containing each type. For example, if your options object requires a «files» parameter that may be a string or an array, you would use .

  • To specify optional, nullable, or NaN-able types, put , , or as one of the valid types in the array. For example, if your options object takes an optional «output» parameter that’s a string, you would use .

• Returns: The normalized options object, consisting of combined with .

• Throws: If the type check fails, an object will be thrown with a human-readable explanation of the type check failure in the parameter. Note that simplebuild task functions are not allowed to throw exceptions, so be sure to catch errors and return via the callback.

Example:

function myTask(userOptions, succeed, fail) {
  try {
    var defaults = {
      timestamp: Date.now()
    };
    var types = {
      files:  String, Array ,
      timestamp: Date,
      output:  String, undefined 
    };
    var options = simplebuild.normalizeOptions(userOptions, defaults, types);
   
    // ... task implemented here ...
  }
  catch (err) {
    return fail(err.message);
  }
}

Convert file globs into files. Given an array or string, this function returns an array of filenames. Any glob (*) or globstar (**) in the parameter is converted to the actual names of files in the filesystem. If any entry in the parameter starts with an exclamation mark (!), then those files will be excluded from the result.

• : A string or array containing file globs.

• Returns: An array of filename strings.

Create the function required for a mapper module. Use it like this:

exports.map = createMapFunction(myMapper);

• : A function that returns a task function, presumably by operating on in some way.

• Returns: A function satisfying the mapper module specification.

Create a new task module based on an existing task module. Similar to , except lower level.

• : The task module to map.

• : A function that returns a task function, presumably by operating on in some way.

• Returns: The new task module.

ООО ПКФ «СБ-КОМПАНИ» на google карте, карта проезда

Возможно вам будут интересны конкуренты ООО ПКФ «СБ-КОМПАНИ»: ОБЩЕСТВО С ОГРАНИЧЕННОЙ ОТВЕТСТВЕННОСТЬЮ «БОЭЗ-КОНТАКТ» | ПЕРВИЧНАЯ ОРГАНИЗАЦИЯ БЕЛГОРОДСКОЙ РЕГИОНАЛЬНОЙ ОРГАНИЗАЦИИ ОБЩЕРОССИЙСКОГО ОБЩЕСТВЕННОГО ОБЪЕДИНЕНИЯ — ПРОФСОЮЗ РАБОТНИКОВ АГРОПРОМЫШЛЕННОГО КОМПЛЕКСА РФ «ПРОФОРГАНИЗАЦИЯ ОАО «ПОРОЗ» ГРАЙВОРОНСКОГО РАЙОНА | ООО «ВЕСНА» | ЗАО «ЩЕЛКУНСКОЕ» | ООО «СКИФАГРО-ДВ»

ООО ПКФ «СБ-КОМПАНИ» юридическое лицо России, зарегистрированное 01.02.2004 в регионе Самарская Область, Россия. Полное название — ОБЩЕСТВО С ОГРАНИЧЕННОЙ ОТВЕТСТВЕННОСТЬЮ ПРОИЗВОДСТВЕННО-КОММЕРЧЕСКАЯ ФИРМА «СБ-КОМПАНИ»; компании при регистрации был присвоен ОГРН 1046300993254 и ИНН 6323066120. Начиная с 2004 фирма расположена по адресу 445004, Самарская Область, Тольятти Город, Базовая Улица, 20.

Сельское хозяйство, охота и предоставление услуг в этих областях является основной видом деятельности компании, включая 49 других видов деятельности.

Данные об владельцах и учредятелях компании ООО ПКФ «СБ-КОМПАНИ» не известны. Компанией используется 0 торговых марок. Все данные о компании ООО ПКФ «СБ-КОМПАНИ» предоставлены из открытых источников, таких как ЕГРЮЛ, ПФР, ФСС, на основе которых можно составить бухгалтерские и финансовые отчеты, проверить кредитную историю компании. За прошлый год оборот компании составил более 263 млн рублей, при уставном капитале в 656000 руб, кредитный рейтинг при этом отличный. В компании ООО ПКФ «СБ-КОМПАНИ» занято менее 10 постоянных сотрудников.

Также вы можете посмотреть отзывы об ООО ПКФ «СБ-КОМПАНИ», открытые вакансии, расположение ООО ПКФ «СБ-КОМПАНИ» на карте. Для более детальной информации вы можете посетить сайт ООО ПКФ «СБ-КОМПАНИ» или запросить данные по контактным данным компании. Информация о компании была обновлена 24.09.2021.

C 26.06.2016 компания ООО ПКФ «СБ-КОМПАНИ» закрыта и деятельность более не ведется.

Usage

This library provides these functions:

• : Run JSHint against a list of files.
• : Run JSHint against a single file (it’s useful for auto-generated build dependencies).
• : Run JSHint against raw source code.

Run JSHint against a list of files. A dot will be written to stdout for each file processed. Any errors will be written to stdout. When there are a large number of files to process, additional worker processes will be spawned to take advantage of additional CPU cores.

• : an object containing the following properties:

  • : a string or array containing the files to check. Globs () and globstars () will be expanded to match files and directory trees respectively. Prepend to exclude files.
  • (optional): Permitted global variables (for use with the option). Each variable should be set to or . If false, the variable is considered read-only.

• : a function to call if the code validates successfully.

• : a function to call if the code does not validate successfully. A simple error message is provided in the parameter, but detailed error messages are written to stdout.

Run JSHint against a single file (it’s useful for auto-generated build dependencies).

• : an object containing the following properties:

  • : a string containing the path to the file to check.
  • (optional): Permitted global variables (for use with the option). Each variable should be set to or . If false, the variable is considered read-only.

• : a function to call if the code validates successfully.

• : a function to call if the code does not validate successfully. A simple error message is provided in the parameter, but detailed error messages are written to stdout.

Run JSHint against raw source code. Any errors will be written to stdout.

• : an object containing the following properties:

  • : a string containing the source code to check.
  • (optional): Permitted global variables (for use with the option). Each variable should be set to or . If false, the variable is considered read-only.

• a function to call if the code validates successfully.

• a function to call if the code does not validate successfully. A simple error message is provided in the parameter, but detailed error messages are output to stdout.

Composability

Simplebuild tasks can be used in any Node.js program, so it’s easy to create tasks that depend on other tasks. If there’s a module that does just what you need, no worries—just it and use it!

Simplebuild also supports «mapper modules» that change the way tasks run, and «extension modules» that interface with other tools. For example, the module adds a header to tasks, and the module converts tasks into promises. Modules can be chained together, providing flexibility and power, without requiring any special programming in the tasks.

In this example, a single addition (the second line) to the «Promises» example above adds a header to all tasks:

Output:

How It Works

Simplebuild’s magic is based on standardized, composable function signatures and a very small supporting library. There are three kinds of Simplebuild modules:

• Task modules do the heavy lifting of task automation. For example, the module uses JSHint to check files for errors. Task modules export functions that follow a standard format: .

• Mapper modules augment task modules in some way. For example, the module adds a header to each task. Mappers output task modules, so they can be added to a build script without requiring individual tasks to be changed. Multiple mapper modules may be chained together.

• Extension modules are like mapper modules, except that they don’t have any restrictions on their input or output. They’re most often used for compatibility with other coding styles or build tools. For example, turns Simplebuild tasks into promises, and loads Simplebuild modules into Grunt.

HTML code analysis

And here you’ll find analysis of HTML code:

Examples

The following examples use Simplebuild modules to lint and test some code. Note how Simplebuild adapts to provide clean, idiomatic solutions for each tool.

module.exports=function(grunt){var simplebuild =require("simplebuild-ext-gruntify.js")(grunt);grunt.initConfig({    JSHint{      files"**/*.js","!node_modules/**/*",      options{ nodetrue},      globals{}},    Mocha{      files"**/_*_test.js","!node_modules/**/*"}});simplebuild.loadNpmTasks("simplebuild-jshint");simplebuild.loadNpmTasks("simplebuild-mocha");grunt.registerTask("default","Lint and test","JSHint","Mocha");};

var jakeify =require("simplebuild-ext-jakeify.js").map;var jshint =jakeify("simplebuild-jshint.js");var mocha =jakeify("simplebuild-mocha.js");task("default","lint","test");desc("Lint everything");jshint.validate.task("lint",{  files"**/*.js","!node_modules/**/*",  options{ nodetrue},  globals{}});desc("Test everything");mocha.runTests.task("test",,{  files"**/_*_test.js","!node_modules/**/*"});

var promisify =require("simplebuild-ext-promisify.js").map;var jshint =promisify("simplebuild-jshint.js");var mocha =promisify("simplebuild-mocha.js");jshint.validate({  files"**/*.js","!node_modules/**/*",  options{ nodetrue},  globals{}}).then(function(){returnmocha.runTests({    files"**/_*_test.js","!node_modules/**/*"});}).then(function(){console.log("\n\nOK");}).fail(function(message){console.log("\n\nFAILED: "+ message);});

Before running the examples:

1. Install Node.js
2. Download the project code
3. Open a command prompt in the project’s root directory
4. Run to install dependencies

To run the examples:

1. Run , , or . (Windows users, use , , or .)

To Do

Things that still need work:

• When creating a module, the options and parameters need a lot of checking in . Writing tests for this behavior is particularly tedious and repetitive. Create helper methods for this that take advantage of descriptors.
• Should messages be written to stderr instead of stdout? Or perhaps some sort of ‘reporter’ spec
• Pull out of simplebuild-jshint into its own module or helper
• Pull and out of simplebuild-jshint (_index_test.js)
• The examples use an out-of-date version of the spec. In particular, they rely on descriptors, which have been removed from the spec for now.

API

In addition to the Simplebuild spec, this npm module is also a library for use by Simplebuild module authors.

Task module authors may wish to use these functions:

• : Check the parameter provided to a simplebuild task.
• : Convert file globs into files.

Mapper and extension module authors may wish to use these functions:

• : Create the function required for a mapper module.
• : Modify every function in a module.

Applies defaults to a simplebuild task’s argument and type-checks the result.

• : The options passed into the task function. Must be an object.

• : The task’s default options. Any parameter that’s present in but not in will be included in the final options object.

• : An object containing the expected types for each option. The parameters in this object correspond to the parameters in the options object. The types are checked on the final options object after the defaults are applied. Any fields that are in the final options and not in the object will not be checked.

  • To specify a language type, use the corresponding object constructor: , , , , , or . For example, if your options include a «name» parameter that’s a string, you would use .

  • To specify an object type, use the object constructor, such as or . You may also pass in the constructor for a custom subclass. For example, if your options object requires a «timestamp» parameter that’s a Date object, you would use .

  • To specify specific object fields, recursively provide another -style object containing the fields you want to check. For example, if your options object requires a «report» object that contains a «verbose» boolean and a «filename» string, you would use .

  • To specify multiple valid types, provide an array containing each type. For example, if your options object requires a «files» parameter that may be a string or an array, you would use .

  • To specify optional, nullable, or NaN-able types, put , , or as one of the valid types in the array. For example, if your options object takes an optional «output» parameter that’s a string, you would use .

• Returns: The normalized options object, consisting of combined with .

• Throws: If the type check fails, an object will be thrown with a human-readable explanation of the type check failure in the parameter. Note that simplebuild task functions are not allowed to throw exceptions, so be sure to catch errors and return via the callback.

Example:

functionmyTask(userOptions,succeed,fail){try{var defaults ={      timestampDate.now()};var types ={      filesString,Array,      timestampDate,      outputString,undefined};var options =simplebuild.normalizeOptions(userOptions, defaults, types);}catch(err){returnfail(err.message);}}

Convert file globs into files. Given an array or string, this function returns an array of filenames. Any glob (*) or globstar (**) in the parameter is converted to the actual names of files in the filesystem. If any entry in the parameter starts with an exclamation mark (!), then those files will be excluded from the result.

• : A string or array containing file globs.

• Returns: An array of filename strings.

Create the function required for a mapper module. Use it like this:

exports.map=createMapFunction(myMapper);

• : A function that returns a task function, presumably by operating on in some way.

• Returns: A function satisfying the mapper module specification.

Create a new task module based on an existing task module. Similar to , except lower level.

• : The task module to map.

• : A function that returns a task function, presumably by operating on in some way.

• Returns: The new task module.

Version History

1.3.0: uses multiple cores when a lot of files need linting. This can result in a big speed boost.

1.2.0: reads files asynchronously and in parallel, which makes it a bit faster.

1.1.0: Better error messages when parameter is incorrect.

1.0.1: Fix: doesn’t try to report non-existent error codes (they’re not present in old versions of JSHint).

1.0.0: Reports warning codes (and error codes) so they can be disabled more easily.

0.3.1: Fix: crashed when error objects had no evidence (first seen in JSHint 2.8.0).

0.3.0: Added as a peer dependency. It no longer needs to be installed separately.

0.2.0: .

0.1.1: Corrected documentation error: options.globals is not actually a JSHint option.

0.1.0: and .

Composability

Simplebuild tasks can be used in any Node.js program, so it’s easy to create tasks that depend on other tasks. If there’s a module that does just what you need, no worries—just it and use it!

Simplebuild also supports «mapper modules» that change the way tasks run, and «extension modules» that interface with other tools. For example, the module adds a header to tasks, and the module converts tasks into promises. Modules can be chained together, providing flexibility and power, without requiring any special programming in the tasks.

In this example, a single addition (the second line) to the «Promises» example above adds a header to all tasks:

var promisify = require("simplebuild-ext-promisify.js")
  .map("simplebuild-map-header.js")
  .map;

var jshint = promisify("simplebuild-jshint");
var mocha = promsifiy("simplebuild-mocha");
...

Output:

License

The MIT License (MIT)

Copyright (c) 2013-2015 James Shore

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

License

The MIT License (MIT)

Copyright (c) 2013-2015 James Shore

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the «Software»), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED «AS IS», WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Formal Specification

Task Modules

Task modules export functions that follow a common format. A task module SHOULD have a name starting with «simplebuild-» but not «simplebuild-map-» or «simplebuild-ext-«. (For example, «simplebuild-yourmodule.js».) All functions exported by a task module MUST be task functions.

Task functions MUST NOT be named , , or use a name ending in . (These restrictions are case-sensitive.) Any other name is permitted. Each task function MUST conform to this signature:

(REQUIRED): Configuration information. Any type of variable may be used, but an object is recommended. If a task function has no configuration, this variable is still required, but may be ignored.

(REQUIRED): Callback function. Each task function MUST call succeed() with no parameters when it finishes successfully.

(REQUIRED): Callback function. Each task function MUST call fail() with a brief human-readable explanation when it fails. The explanation SHOULD be less than 50 characters.

Task Behavior

Task functions MUST NOT return values or throw exceptions. Instead, either the or callback MUST be called exactly once when the task is complete. The callback may be called synchronously or asynchronously.

Tasks that fail SHOULD provide a detailed explanation suitable for debugging the problem. If the explanation is too long to fit in the 50-character failure mesage, the task SHOULD write the details to before failing. (Note that calling is a convenient way of writing to .)

Tasks that succeed SHOULD NOT write to by default. They MAY write more if configured to do so with the parameter.

Tasks that are slow or long-running MAY provide minimalistic progress output (such as periods) but SHOULD NOT provide more detailed information by default. They MAY provide more if configured to do so with the parameter.

Tasks SHOULD NOT write to under any circumstances.

Mapper Modules

Mapper modules export a single function, , that transforms a Simplebuild module in some way. A mapper module SHOULD have a name starting with . (For example, .)

Mapper modules MUST export only one function, named . The function call itself SHOULD NOT have any side effects, but the functions returns may. Mapper modules SHOULD use the API call defined in the module to create the function.

The function MUST take a single parameter and return an object, as follows. These requirements are handled automatically by .

• When the parameter is an object with a single key named , it will be considered to be a mapper module. In this case, the function MUST return a mapper module. The returned module’s function MUST wrap the provided mapper module so that calling is equivalent to calling

• When the parameter is any other object, it will be considered to be a task module. In this case, the function MUST return a task module. The returned task module SHOULD have different functions and/or behavior than the provided task module.

• When the parameter is a string, it will be considered to be an Node.js module. In this case, the function MUST use the Node.js API call to load the module, then apply the above rules.

Extension Modules

Extension modules extend the capabilities of Simplebuild. An extension module SHOULD have a name starting with «simplebuild-ext-» (for example, «simplebuild-ext-yourextension.js»).

Extension modules are unrestricted. They may export any number of functions, with any signatures, that do anything. When a function supports loading task modules by name, it SHOULD also support mapper modules as well. The API call defined in the module may be helpful here.

Похожие записи:

Уборка придомовой территории Монолитная фундаментная плита своими руками Анаэробный герметик Придомовая территория частного дома Глава iv уход за бетоном и контроль его качества Правила эксплуатации металлических резервуаров для нефти и нефтепродуктов и руководство по их ремонту