Home
last modified time | relevance | path

Searched +full:node +full:- +full:api (Results 1 – 25 of 1047) sorted by relevance

12345678910>>...42

/third_party/node/
DMakefile1 -include config.mk
10 STAGINGSERVER ?= node-www
12 OSTYPE := $(shell uname -s | tr '[A-Z]' '[a-z]')
13 COVTESTS ?= test-cov
16 GNUMAKEFLAGS += --no-print-directory
23 PARALLEL_ARGS = -j $(JOBS)
25 PARALLEL_ARGS = -J
29 TAP_V8 := --junitout $(PWD)/v8-tap.xml
30 TAP_V8_INTL := --junitout $(PWD)/v8-intl-tap.xml
31 TAP_V8_BENCHMARKS := --junitout $(PWD)/v8-benchmarks-tap.xml
[all …]
Dvcbuild.bat8 if /i "%1"=="--help" goto help
9 if /i "%1"=="-help" goto help
12 if /i "%1"=="-?" goto help
13 if /i "%1"=="--?" goto help
19 set NATIVE_SUITES=addons js-native-api node-api
24 @rem Same as the test-ci target in Makefile
74 :next-arg
75 if "%1"=="" goto args-done
76 if /i "%1"=="debug" set config=Debug&goto arg-ok
77 if /i "%1"=="release" set config=Release&set ltcg=1&set cctest=1&goto arg-ok
[all …]
/third_party/node/doc/guides/
Dadding-new-napi-api.md1 # Contributing a new API to N-API
3 N-API is the next-generation ABI-stable API for native modules.
4 While improving the API surface is encouraged and welcomed, the following are
6 N-API API.
8 * A new API **must** adhere to N-API API shape and spirit.
9 * **Must** be a C API.
15 * **Must** be a necessary API and not a nice to have. Convenience APIs
16 belong in node-addon-api.
17 * **Must** not change the signature of an existing N-API API or break
18 ABI compatibility with other versions of Node.js.
[all …]
Ddiagnostic-tooling-support-tiers.md3 Diagnostic tooling is important to the consumers of Node.js. It is used both
8 The Node.js project has assessed the tools and the APIs which support those
12 * Tier 1 - Must always be working(CI tests passing) for all
13 Current and LTS Node.js releases. A release will not be shipped if the test
14 suite for the tool/API is not green. To be considered for inclusion
16 must exist in the Node.js CI so that it can be run as part of the release
19 release branches should break this tool/API if the next major release
25 * The tool must have a guide or other documentation in the Node.js GitHub
28 * The tool must only be using APIs exposed by Node.js as opposed to
32 * Tier 2 - Must be working(CI tests passing) for all
[all …]
Dcollaborator-guide.md1 # Node.js Collaborator Guide
5 * [Issues and pull requests](#issues-and-pull-requests)
6 * [Welcoming first-time contributors](#welcoming-first-time-contributors)
7 * [Closing issues and pull requests](#closing-issues-and-pull-requests)
8 * [Author ready pull requests](#author-ready-pull-requests)
9 * [Handling own pull requests](#handling-own-pull-requests)
10 * [Accepting modifications](#accepting-modifications)
11 * [Code reviews](#code-reviews)
12 * [Consensus seeking](#consensus-seeking)
13 * [Waiting for approvals](#waiting-for-approvals)
[all …]
/third_party/node/deps/npm/node_modules/safer-buffer/
DReadme.md1-buffer [![travis][travis-image]][travis-url] [![npm][npm-image]][npm-url] [![javascript style gui…
3 [travis-image]: https://travis-ci.org/ChALkeR/safer-buffer.svg?branch=master
4 [travis-url]: https://travis-ci.org/ChALkeR/safer-buffer
5 [npm-image]: https://img.shields.io/npm/v/safer-buffer.svg
6 [npm-url]: https://npmjs.org/package/safer-buffer
7 [standard-image]: https://img.shields.io/badge/code_style-standard-brightgreen.svg
8 [standard-url]: https://standardjs.com
9 [secuirty-image]: https://img.shields.io/badge/Security-Responsible%20Disclosure-green.svg
10 [secuirty-url]: https://github.com/nodejs/security-wg/blob/master/processes/responsible_disclosure_…
12 Modern Buffer API polyfill without footguns, working on Node.js from 0.8 to current.
[all …]
DPorting-Buffer.md1 # Porting to the Buffer.from/Buffer.alloc API
6 - [Variant 1: Drop support for Node.js ≤ 4.4.x and 5.0.0 — 5.9.x.](#variant-1) (*recommended*)
7 - [Variant 2: Use a polyfill](#variant-2)
8 - [Variant 3: manual detection, with safeguards](#variant-3)
12 Just run `grep -nrE '[^a-zA-Z](Slow)?Buffer\s*\(' --exclude-dir node_modules`.
17 ### Finding problematic bits of code using Node.js 8
19 If you’re using Node.js ≥ 8.0.0 (which is recommended), Node.js exposes multiple options that help …
21 - `--trace-warnings` will make Node.js show a stack trace for this warning and other warnings that …
22 - `--trace-deprecation` does the same thing, but only for deprecation warnings.
23 - `--pending-deprecation` will show more types of deprecation warnings. In particular, it will show…
[all …]
/third_party/node/tools/node_modules/eslint/node_modules/safer-buffer/
DReadme.md1-buffer [![travis][travis-image]][travis-url] [![npm][npm-image]][npm-url] [![javascript style gui…
3 [travis-image]: https://travis-ci.org/ChALkeR/safer-buffer.svg?branch=master
4 [travis-url]: https://travis-ci.org/ChALkeR/safer-buffer
5 [npm-image]: https://img.shields.io/npm/v/safer-buffer.svg
6 [npm-url]: https://npmjs.org/package/safer-buffer
7 [standard-image]: https://img.shields.io/badge/code_style-standard-brightgreen.svg
8 [standard-url]: https://standardjs.com
9 [secuirty-image]: https://img.shields.io/badge/Security-Responsible%20Disclosure-green.svg
10 [secuirty-url]: https://github.com/nodejs/security-wg/blob/master/processes/responsible_disclosure_…
12 Modern Buffer API polyfill without footguns, working on Node.js from 0.8 to current.
[all …]
DPorting-Buffer.md1 # Porting to the Buffer.from/Buffer.alloc API
6 - [Variant 1: Drop support for Node.js ≤ 4.4.x and 5.0.0 — 5.9.x.](#variant-1) (*recommended*)
7 - [Variant 2: Use a polyfill](#variant-2)
8 - [Variant 3: manual detection, with safeguards](#variant-3)
12 Just run `grep -nrE '[^a-zA-Z](Slow)?Buffer\s*\(' --exclude-dir node_modules`.
17 ### Finding problematic bits of code using Node.js 8
19 If you’re using Node.js ≥ 8.0.0 (which is recommended), Node.js exposes multiple options that help …
21 - `--trace-warnings` will make Node.js show a stack trace for this warning and other warnings that …
22 - `--trace-deprecation` does the same thing, but only for deprecation warnings.
23 - `--pending-deprecation` will show more types of deprecation warnings. In particular, it will show…
[all …]
/third_party/node/doc/api/
Ddeprecations.md3 <!--introduced_in=v7.7.0-->
4 <!-- type=misc -->
6 Node.js may deprecate APIs for any of the following reasons:
8 * Use of the API is unsafe.
9 * An improved alternative API is available.
10 * Breaking changes to the API are expected in a future major release.
12 Node.js utilizes three kinds of Deprecations:
14 * Documentation-only
16 * End-of-Life
18 A Documentation-only deprecation is one that is expressed only within the
[all …]
Dn-api.md1 # N-API
3 <!--introduced_in=v8.0.0-->
4 <!-- type=misc -->
6 > Stability: 2 - Stable
8 N-API (pronounced N as in the letter, followed by API)
9 is an API for building native Addons. It is independent from
11 Node.js itself. This API will be Application Binary Interface (ABI) stable
12 across versions of Node.js. It is intended to insulate Addons from
14 compiled for one major version to run on later major versions of Node.js without
15 recompilation. The [ABI Stability][] guide provides a more in-depth explanation.
[all …]
Daddons.md3 <!--introduced_in=v0.10.0-->
4 <!-- type=misc -->
6 _Addons_ are dynamically-linked shared objects written in C++. The
7 [`require()`][require] function can load addons as ordinary Node.js modules.
10 There are three options for implementing addons: N-API, nan, or direct
11 use of internal V8, libuv and Node.js libraries. Unless there is a need for
12 direct access to functionality which is not exposed by N-API, use N-API.
13 Refer to [C/C++ addons with N-API](n-api.html) for more information on N-API.
15 When not using N-API, implementing addons is complicated,
18 * V8: the C++ library Node.js uses to provide the
[all …]
Dtracing.md3 <!--introduced_in=v7.7.0-->
5 > Stability: 1 - Experimental
7 <!-- source_link=lib/trace_events.js -->
10 generated by V8, Node.js core, and userspace code.
12 Tracing can be enabled with the `--trace-event-categories` command-line flag
13 or by using the `trace_events` module. The `--trace-event-categories` flag
14 accepts a list of comma-separated category names.
18 * `node`: An empty placeholder.
19 * `node.async_hooks`: Enables capture of detailed [`async_hooks`][] trace data.
22 * `node.bootstrap`: Enables capture of Node.js bootstrap milestones.
[all …]
/third_party/node/test/
DREADME.md1 # Node.js Core Tests
3 This directory contains code and data used to test the Node.js implementation.
6 directory, see [the guide on writing tests](../doc/guides/writing-tests.md).
9 [the contributing guide](../doc/guides/contributing/pull-requests.md#step-6-test).
11 For the tests to run on Windows, be sure to clone Node.js source code with the
17 | ------------------- | --------------- | --------------- |
18 | `abort` | Yes | Tests for when the `--abort-on-uncaught-exception` flag i…
19 | `addons` | Yes | Tests for [addon](https://nodejs.org/api/addons.html) fun…
20 | `async-hooks` | Yes | Tests for [async_hooks](https://nodejs.org/api/async_hook…
23 | `code-cache` | No | Tests for a Node.js binary compiled with V8 code cache. |
[all …]
/third_party/node/deps/npm/node_modules/har-validator/
DREADME.md3 [![license][license-img]][license-url]
4 [![version][npm-img]][npm-url]
5 [![super linter][super-linter-img]][super-linter-url]
6 [![test][test-img]][test-url]
7 [![release][release-img]][release-url]
9 [license-url]: LICENSE
10 [license-img]: https://badgen.net/github/license/ahmadnassri/node-har-validator
12 [npm-url]: https://www.npmjs.com/package/har-validator
13 [npm-img]: https://badgen.net/npm/v/har-validator
15 [super-linter-url]: https://github.com/ahmadnassri/node-har-validator/actions?query=workflow%3Asupe…
[all …]
/third_party/node/deps/npm/node_modules/node-fetch-npm/
DREADME.md2 node-fetch-npm
5 [![npm version][npm-image]][npm-url]
6 [![build status][travis-image]][travis-url]
7 [![coverage status][codecov-image]][codecov-url]
9 A light-weight module that brings `window.fetch` to Node.js
11 `node-fetch-npm` is a fork of [`node-fetch`](https://npm.im/node-fetch) used in
12 npm itself, through [`make-fetch-happen`](https://npm.im/make-fetch-happen). It
14 `node-fetch`'s own design goals (such as picking a specific cookie library,
17 This library is *not a replacement* for `node-fetch`, nor does it intend to
25Node.js to run browser-specific [Fetch polyfill](https://github.com/github/fetch), why not go from…
[all …]
/third_party/node/.github/workflows/
Dpythonpackage.yml7 runs-on: ubuntu-latest
9 fail-fast: false
10 max-parallel: 1
12 python-version: [3.8] # [2.7, 3.5, 3.6, 3.7]
14 - uses: actions/checkout@v2
15 - name: Set up Python ${{ matrix.python-version }}
16 uses: actions/setup-python@v1
18 python-version: ${{ matrix.python-version }}
19 - name: Compile Node.js
22 make -j2 V=1
[all …]
/third_party/icu/ohos_icu4j/src/main/java/ohos/global/icu/util/
DStringTrieBuilder.java6 * Copyright (C) 2011-2014, International Business Machines
49 * @deprecated This API is ICU internal only.
56 * @deprecated This API is ICU internal only.
77 * @deprecated This API is ICU internal only.
90 // because it makes registerNode() return the input node in buildImpl()
94 // In either case we need to fix-up linear-match nodes (for their maximum length) in buildImpl()
96 // runtime-equivalent nodes), but the HashMap/hashCode()/equals() are omitted for in buildImpl()
116 root.markRightEdgesFirst(-1); in buildImpl()
122 * @deprecated This API is ICU internal only.
134 * Makes sure that there is only one unique node registered that is
[all …]
/third_party/node/src/
Djs_native_api_v8_internals.h4 // The V8 implementation of N-API, including `js_native_api_v8.h` uses certain
8 // may also define `NAPI_VERSION` and set it to the version of N-API to be
11 // In the case of the Node.js implementation of N-API some of the idioms are
12 // imported directly from Node.js by including `node_internals.h` below. Others
13 // are bridged to remove references to the `node` namespace. `node_version.h`,
21 node::arraysize((array))
24 node::FIXED_ONE_BYTE_STRING((isolate), (string))
27 (node::Environment::GetCurrent((context))->napi_ ## suffix())
34 using PersistentToLocal = node::PersistentToLocal;
DREADME.md1 # Node.js C++ codebase
3 Hi! �� You’ve found the C++ code backing Node.js. This README aims to help you
9 Node.js has a document detailing its [C++ coding style][]
12 ## V8 API documentation
14 A lot of the Node.js codebase is around what the underlying JavaScript engine,
15 V8, provides through its API for embedders. Knowledge of this API can also be
16 useful when working with native addons for Node.js written in C++, although for
17 new projects [N-API][] is typically the better alternative.
19 V8 does not provide much public API documentation beyond what is
23 * On GitHub: [`v8.h` in Node.js master][]
[all …]
/third_party/FreeBSD/sys/compat/linuxkpi/common/include/linux/
Dhrtimer.h1 /*-
25 …* $FreeBSD: releng/12.2/sys/compat/linuxkpi/common/include/linux/hrtimer.h 334482 2018-06-01 11:33…
71 s64 tv64; /**< Scheduled time for 64-bit CPU systems. */
73 s32 sec, usec; /**< Scheduled time for 32-bit CPU systems. */
79 * Structure of a node in a high-resolution timer queue.
82 unsigned int node; /**< Not in use temporarily. */ member
87 * Enumerative structure of the high-resolution timer mode arguments.
97 * Enumerative structure of the return type of a high-resolution timer timeout callback function.
107 * Define the function handler type of a high-resolution timer timeout callback function.
113 * Structure of parameters of a high-resolution timer API.
[all …]
/third_party/parse5/packages/parse5-serializer-stream/docs/
Dindex.md3 Streaming AST node to an HTML serializer. A [readable stream](https://nodejs.org/api/stream.html#st…
9 const SerializerStream = require('parse5-serializer-stream');
27 See: [readable stream API](https://nodejs.org/api/stream.html#stream_class_stream_readable).
29 ---
37 ⊕ **new SerializerStream**(node: *Node*, options?: *[SerializerOptions](../../parse5/docs/options/s…
39 Streaming AST node to an HTML serializer. A readable stream.
44 | ------ | ------ | ------ |
45 | node | Node | Node to serialize. |
46 | `Optional` options | [SerializerOptions](../../parse5/docs/options/serializer-options.md) | Seri…
/third_party/node/tools/eslint-rules/
Ddocumented-errors.js5 const { isDefiningError } = require('./rules-utils.js');
7 const doc = fs.readFileSync(path.resolve(__dirname, '../../doc/api/errors.md'),
18 function errorForNode(node) { argument
19 return node.expression.arguments[0].value;
25 ExpressionStatement: function(node) { argument
26 if (!isDefiningError(node) || !errorForNode(node)) return;
27 const code = errorForNode(node);
29 const message = `"${code}" is not documented in doc/api/errors.md`;
30 context.report({ node, message }); property
34 `doc/api/errors.md does not have an anchor for "${code}"`;
[all …]
/third_party/libffi/doc/
Dlibffi.info6 Copyright (C) 2008-2019 Anthony Green and Red Hat, Inc.
27 INFO-DIR-SECTION Development
28 START-INFO-DIR-ENTRY
30 END-INFO-DIR-ENTRY
33 File: libffi.info, Node: Top, Next: Introduction, Up: (dir)
41 Copyright (C) 2008-2019 Anthony Green and Red Hat, Inc.
70 File: libffi.info, Node: Introduction, Next: Using libffi, Prev: Top, Up: Top
86 told at run-time about the number and types of arguments used to call a
103 File: libffi.info, Node: Using libffi, Next: Missing Features, Prev: Introduction, Up: Top
110 * The Basics:: The basic libffi API.
[all …]
/third_party/node/deps/npm/node_modules/string_decoder/node_modules/safe-buffer/
DREADME.md1-buffer [![travis][travis-image]][travis-url] [![npm][npm-image]][npm-url] [![downloads][downloads
3 [travis-image]: https://img.shields.io/travis/feross/safe-buffer/master.svg
4 [travis-url]: https://travis-ci.org/feross/safe-buffer
5 [npm-image]: https://img.shields.io/npm/v/safe-buffer.svg
6 [npm-url]: https://npmjs.org/package/safe-buffer
7 [downloads-image]: https://img.shields.io/npm/dm/safe-buffer.svg
8 [downloads-url]: https://npmjs.org/package/safe-buffer
9 [standard-image]: https://img.shields.io/badge/code_style-standard-brightgreen.svg
10 [standard-url]: https://standardjs.com
12 #### Safer Node.js Buffer API
[all …]

12345678910>>...42