Home
last modified time | relevance | path

Searched refs:JS (Results 1 – 25 of 242) sorted by relevance

12345678910

/third_party/jerryscript/docs/
D09.EXT-REFERENCE-ARG.md42 its corresponding JS-to-C mapping and other related information.
49 const jerry_char_t **name_p; /**< property name list of the JS object */
65 JS-to-C mappings and count.
96 This enables complex validation like handling different JS function signatures,
121 Enum that indicates whether an argument is allowed to be coerced into the expected JS type.
189 Validate the this value and the JS arguments, and assign them to the native arguments.
204 - `js_arg_p` - points to the array with JS arguments.
218 /* JS signature: function (requiredBool, requiredString, optionalNumber) */
290 - `js_arg_p` - points to the array with JS arguments.
305 Validate the properties of a JS object and assign them to the native arguments.
[all …]
D03.API-EXAMPLE.md158 /* Check if there is any JS code parse error */
243 /* Create a "print" JS string */
245 /* Create a function from a native C method (this function will be called from JS) */
303 argument (which probably comes from a JavaScript source) to a JS string and prints it out to the st…
327 /* Convert the first argument to a string (JS "toString" operation) */
353 const jerry_char_t script[] = "print ('Hello from JS!');";
363 /* Create a "print" JS string */
365 /* Create a function from a native C method (this function will be called from JS) */
411 …s correct the application should print out the string passed for the `print` method in the JS code:
438 const jerry_char_t script[] = "print ('Hello from JS with ext!');";
[all …]
/third_party/jsframework/
DREADME.md7 - `./main/`：JS bundle parsing, data methods, event methods, reactivity, etc.
8 - `./preparation/`：JS framework initialization
13 - `BUILD.gn`：compiling file of JS UI framework for NinjaJS
14 - `build_jsmock_system_plugin.js, build_strip_native_min.js`: build JS framework
15 - `js_framework_build.sh`：script file for JS framework building
53 There are two ways for building JS framework:
/third_party/node/test/fixtures/es-modules/
Dwasm-dep.mjs4 state = 'WASM JS Function Executed';
8 export let state = 'JS Function Executed';
11 strictEqual(state, 'JS Function Executed');
/third_party/typescript/tests/baselines/reference/
Dshebang.types3 var foo = 'I wish the generated JS to be executed in node';
5 >'I wish the generated JS to be executed in node' : "I wish the generated JS to be executed in node"
DglobalThisPropertyAssignment.types13 // should work in JS
21 // should work in JS (even though it's a secondary declaration)
DglobalThisPropertyAssignment.errors.txt7 // should work in JS
11 // should work in JS (even though it's a secondary declaration)
DemitBOM.sourcemap.txt11 >>>// JS and d.ts output should have a BOM but not the sourcemap
15 2 >// JS and d.ts output should have a BOM but not the sourcemap
DglobalThisPropertyAssignment.symbols10 // should work in JS
14 // should work in JS (even though it's a secondary declaration)
DemitBOM.types2 // JS and d.ts output should have a BOM but not the sourcemap
/third_party/skia/modules/pathkit/npm-asmjs/
DREADME.md12 PathKit comes in two parts, a JS loader and the actual WASM code. The JS loader creates
14 is used to tell the JS loader where to find the .js.mem file. By default, it will
26 WebPack's support for asm.js should be straight-forward, since it's just another JS library. PathKi…
29 In the JS code, use require():
/third_party/flutter/skia/modules/pathkit/npm-asmjs/
DREADME.md12 PathKit comes in two parts, a JS loader and the actual WASM code. The JS loader creates
14 is used to tell the JS loader where to find the .js.mem file. By default, it will
26 WebPack's support for asm.js should be straight-forward, since it's just another JS library. PathKi…
29 In the JS code, use require():
/third_party/flatbuffers/docs/source/
DJavaScriptUsage.md22 1. Run `npm run compile` from the main folder to generate JS files from TS.
31 Due to the complexity related with large amounts of JS flavors and module types,
32 native JS support has been replaced in 2.0 by transpilation from TypeScript.
35 transpile your sources to desired JS flavor. The minimal steps to get up and
36 running with JS are:
39 1. Transpile resulting TS files to desired JS flavor using `tsc` (see
/third_party/node/test/fixtures/wpt/resources/webidl2/
DREADME.md10 both in Node and in the browser (the parser likely works in other JS environments, but
35 ```JS
77 ```JS
106 ```JS
139 ```JS
167 ```JS
194 ```JS
224 ```JS
275 ```JS
299 ```JS
[all …]
/third_party/ejdb/src/bindings/ejdb2_react_native/tests/android/app/
Dbuild.gradle15 * // the name of the generated asset file containing your JS bundle
21 * // whether to bundle JS and assets in debug mode
24 * // whether to bundle JS and assets in release mode
27 * // whether to bundle JS and assets in another build variant (if configured).
46 * // where to put the JS bundle asset in debug mode
49 * // where to put the JS bundle asset in release mode
60 * // by default the gradle tasks are skipped if none of the JS files or assets change; this means
63 * // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
/third_party/flutter/skia/modules/pathkit/npm-wasm/
DREADME.md12 PathKit comes in two parts, a JS loader and the actual WASM code. The JS loader creates
14 is used to tell the JS loader where to find the .wasm file. By default, it will
29 In the JS code, use require():
/third_party/skia/modules/pathkit/npm-wasm/
DREADME.md12 PathKit comes in two parts, a JS loader and the actual WASM code. The JS loader creates
14 is used to tell the JS loader where to find the .wasm file. By default, it will
29 In the JS code, use require():
/third_party/flutter/skia/specs/web-img-decode/
DREADME.md1 JS image decode
10 and have JS turn it into a grayscale version (no backend server).
/third_party/skia/specs/web-img-decode/
DREADME.md1 JS image decode
10 and have JS turn it into a grayscale version (no backend server).
/third_party/grpc/doc/
Dssl-performance.md32 Node.JS | n/a | Linux | :heavy_check_mark:
33 Node.JS | n/a | MacOS | :heavy_check_mark:
34 Node.JS | n/a | Windows | :x:
/third_party/node/deps/npm/node_modules/deep-extend/
DCHANGELOG.md22 - Support older Node.JS versions (`v0.11.x` and `v0.10.x`);
46 - Strict JS mode.
/third_party/node/deps/cjs-module-lexer/
DREADME.md5 A [very fast](#benchmarks) JS CommonJS module syntax lexer used to detect the most likely list of n…
11 …mprehensively handles the JS language grammar while remaining small and fast. - ~90ms per MB of JS…
359 ### JS Grammar Support
363 * Always correctly parses valid JS source, but may parse invalid JS source without errors.
371 JS Build:
/third_party/libphonenumber/javascript/
DREADME.md97 1. JS port does not support extracting phone-numbers from text (findNumbers).
98 2. JS port does not have an offline phone number geocoder.
99 3. JS port of PhoneNumberUtil does not handle all digits, only a subset (JavaScript has no equivale…
/third_party/flatbuffers/js/
DREADME.md1 This folder is intentionally empty and will contain transpiled js modules in Common JS format after…
/third_party/typescript/.github/ISSUE_TEMPLATE/
DFeature_request.md37 * [ ] This could be implemented without emitting different JS based on the types of the expressions
38 …library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)

12345678910