file stringlengths 16 94 | text stringlengths 32 24.4k | vector list |
|---|---|---|
javascript/reference/errors/cant_define_property_object_not_extensible/index.md | JavaScript - Errors - Cant define property object not extensible - Message:
Example:
TypeError: Cannot add property x, object is not extensible (V8-based)
TypeError: Cannot define property x, object is not extensible (V8-based)
TypeError: can't define property "x": Object is not extensible (Firefox)
TypeError: Attemp... | [
-0.8712013959884644,
0.07548369467258453,
-1.0106829404830933,
0.4458577036857605,
-0.9533219933509827,
-0.8329893946647644,
0.7833960056304932,
1.0557104349136353,
0.3850928246974945,
-0.9244621396064758,
0.39228788018226624,
-0.3296959698200226,
-0.4537208378314972,
-0.9478153586387634,
... |
javascript/reference/errors/cant_define_property_object_not_extensible/index.md | JavaScript - Errors - Cant define property object not extensible - Error type:
`TypeError` | [
-0.9196909666061401,
0.4094598889350891,
-0.7430034875869751,
0.04464256390929222,
-0.7745351791381836,
-0.5352504253387451,
0.5442337989807129,
1.643933892250061,
-0.056008607149124146,
-0.7735561728477478,
0.6841233372688293,
-0.01877812296152115,
-0.10417895019054413,
-0.880740165710449... |
javascript/reference/errors/cant_define_property_object_not_extensible/index.md | JavaScript - Errors - Cant define property object not extensible - What went wrong?:
Usually, an object is extensible and new properties can be added to it. However, in this case the object isn't extensible, so that it will never have properties beyond the ones it had at the time it was marked as non-extensible. You c... | [
-1.1657418012619019,
0.2352009117603302,
-0.7550095319747925,
0.5707348585128784,
0.045520830899477005,
-1.9053165912628174,
0.4229391813278198,
1.3596735000610352,
0.1683494746685028,
-0.4636625051498413,
-0.16313262283802032,
-0.08182301372289658,
-0.4723043143749237,
-0.5938358902931213... |
javascript/reference/errors/cant_define_property_object_not_extensible/index.md | JavaScript - Errors - Cant define property object not extensible - Examples - Adding new properties to a non-extensible objects:
In strict mode, attempting to add new properties to a non-extensible object via assignment throws a `TypeError`. In sloppy mode, the addition of the "x" property is silently ignored.
Exampl... | [
-1.1100372076034546,
0.1636330932378769,
-1.0845062732696533,
0.4187142848968506,
-0.5780506134033203,
-0.8527151346206665,
1.0305237770080566,
0.6647160649299622,
0.6479651927947998,
-0.6232503056526184,
-0.31892815232276917,
-0.2907319664955139,
-0.628545343875885,
-0.9672982096672058,
... |
javascript/reference/errors/cant_define_property_object_not_extensible/index.md | JavaScript - Errors - Cant define property object not extensible - Examples - Non-extensible objects created by other means:
The `Object.seal()` and `Object.freeze()` methods also create non-extensible objects—they just have additional restrictions on modifying existing properties as well.
Example:
"use strict";
co... | [
-0.7521918416023254,
0.5782290101051331,
-0.9705609679222107,
0.5420160293579102,
-0.1161920577287674,
-1.1983070373535156,
0.47347915172576904,
1.7257236242294312,
-0.0014583650045096874,
0.13464857637882233,
-0.27801576256752014,
-0.33622512221336365,
-0.3854905366897583,
-1.072264432907... |
javascript/reference/errors/cant_define_property_object_not_extensible/index.md | JavaScript - Errors - Cant define property object not extensible - Examples - Fixing the error:
There are three ways to fix this error: you can remove the property addition entirely if you don't need it, you can copy the existing properties to a new extensible object, or you can add the property before making the obje... | [
-0.6651017665863037,
0.6534249782562256,
-0.7321202754974365,
0.47492262721061707,
-0.46559879183769226,
-1.7090141773223877,
0.7221868634223938,
0.8822474479675293,
0.29678472876548767,
-0.3078918159008026,
-0.6588544845581055,
0.031209290027618408,
-0.6027929782867432,
-0.709905505180358... |
javascript/reference/errors/duplicate_parameter/index.md | JavaScript - Errors - Duplicate parameter:
The JavaScript exception "duplicate formal argument x" or "duplicate argument names not allowed in this context" occurs when a function creates two or more parameter `bindings` with the same name, and the function is not a non-strict function with only simple parameters. | [
-0.34969261288642883,
-0.23706002533435822,
-1.1219160556793213,
1.162659764289856,
-0.7677001357078552,
-0.9764143228530884,
0.8871814608573914,
0.43413737416267395,
-1.0530818700790405,
-0.7890902161598206,
-0.8150793313980103,
-0.737528920173645,
0.23972348868846893,
-0.4537269473075866... |
javascript/reference/errors/duplicate_parameter/index.md | JavaScript - Errors - Duplicate parameter - Message:
Example:
SyntaxError: Duplicate parameter name not allowed in this context (V8-based)
SyntaxError: duplicate formal argument x (Firefox)
SyntaxError: duplicate argument names not allowed in this context (Firefox)
SyntaxError: Cannot declare a parameter named 'x' in... | [
-0.12584610283374786,
0.15004810690879822,
-1.1638672351837158,
-0.08431989699602127,
-1.1725263595581055,
-1.1095259189605713,
1.2424204349517822,
0.8565543293952942,
-0.18334540724754333,
-0.12565971910953522,
-0.06430500000715256,
-0.17700281739234924,
0.13840579986572266,
-0.3755209445... |
javascript/reference/errors/duplicate_parameter/index.md | JavaScript - Errors - Duplicate parameter - Error type:
`SyntaxError` | [
-0.525120735168457,
0.29300880432128906,
-1.000031590461731,
0.10902447998523712,
-0.8112315535545349,
-0.34498322010040283,
1.6239172220230103,
2.2200493812561035,
-0.42832180857658386,
-1.026581048965454,
-0.08163414150476456,
-0.008230771869421005,
0.22769954800605774,
-0.01432148553431... |
javascript/reference/errors/duplicate_parameter/index.md | JavaScript - Errors - Duplicate parameter - What went wrong?:
Having two formal parameters of the same name is likely a mistake—the second occurrence would cause the first occurrence to be inaccessible through the parameter name. In legacy JavaScript, this was allowed. Therefore, to not break existing code, this is on... | [
-0.4002959430217743,
0.6325086951255798,
-1.1376323699951172,
0.6216697692871094,
-0.22724008560180664,
-1.2319164276123047,
1.1192375421524048,
0.4422454237937927,
-1.1153454780578613,
-0.032951775938272476,
-0.9691036343574524,
-0.5752729773521423,
0.049908075481653214,
-0.50010931491851... |
javascript/reference/errors/duplicate_parameter/index.md | JavaScript - Errors - Duplicate parameter - Examples - Invalid cases:
Example:
"use strict";
function add(x, x) {
// How can you access both "x" parameters?
// SyntaxError: duplicate formal argument x
}
Example:
function doSomething(name, { name }) {
// How can you access both "name" parameters?
// SyntaxE... | [
-0.2415182739496231,
0.37068405747413635,
-0.8217021822929382,
0.5620529651641846,
-0.3887772560119629,
-1.1028943061828613,
1.4834002256393433,
0.8694809675216675,
-0.763886570930481,
-0.2768346071243286,
-0.13031086325645447,
-0.2724686861038208,
0.04863475263118744,
-0.5620597004890442,... |
javascript/reference/errors/duplicate_parameter/index.md | JavaScript - Errors - Duplicate parameter - Examples - Valid cases:
Example:
function doSomething(operationName, { name: userName }) {
// You can access both "operationName" and "userName" parameters.
}
function doSomething(name, user) {
// You can access both "name" and "user.name" parameters.
} | [
-0.020122084766626358,
0.48365241289138794,
-1.9266165494918823,
0.6849486827850342,
-0.016185212880373,
-0.28484004735946655,
1.4098657369613647,
0.6720370650291443,
-0.863264799118042,
-0.5258525609970093,
-0.3126802146434784,
-0.7027965188026428,
0.2625754773616791,
-1.1018211841583252,... |
javascript/reference/errors/string_literal_eol/index.md | JavaScript - Errors - String literal EOL:
The JavaScript error "string literal contains an unescaped line break" occurs when there is an unterminated string literal somewhere. String literals must be enclosed by single (`'`) or double (`"`) quotes and cannot split across multiple lines. | [
-2.0406181812286377,
0.47333618998527527,
-0.01520535908639431,
-0.2786561846733093,
-0.11231537908315659,
-0.8725786209106445,
0.5896113514900208,
0.8946991562843323,
-0.6073582768440247,
-0.3220376670360565,
-0.014086304232478142,
-0.6632280945777893,
-0.15399016439914703,
-0.62437593936... |
javascript/reference/errors/string_literal_eol/index.md | JavaScript - Errors - String literal EOL - Message:
Example:
SyntaxError: Invalid or unexpected token (V8-based)
SyntaxError: '' string literal contains an unescaped line break (Firefox)
SyntaxError: Unexpected EOF (Safari) | [
-1.6903021335601807,
0.28666532039642334,
-0.0702005922794342,
-1.0130923986434937,
-0.4225320816040039,
-1.423778772354126,
1.0419975519180298,
1.126478910446167,
-0.3811556398868561,
-0.5086202621459961,
0.23652184009552002,
-0.471746027469635,
-0.11731801182031631,
-0.49106869101524353,... |
javascript/reference/errors/string_literal_eol/index.md | JavaScript - Errors - String literal EOL - Error type:
`SyntaxError` | [
-1.0789669752120972,
0.4975528120994568,
0.06422027200460434,
-0.7373883724212646,
-0.6021812558174133,
-1.2623111009597778,
1.150402307510376,
2.290785312652588,
-0.33337798714637756,
-0.5708217024803162,
0.5084745287895203,
-0.5374453067779541,
-0.06407033652067184,
-0.37358272075653076,... |
javascript/reference/errors/string_literal_eol/index.md | JavaScript - Errors - String literal EOL - What went wrong?:
There is an unterminated string literal somewhere. String literals must be enclosed by single (`'`) or double (`"`) quotes. JavaScript makes no distinction between single-quoted strings and double-quoted strings. Escape sequences work in strings created with... | [
-2.7390074729919434,
0.6025585532188416,
0.1720399260520935,
-0.7777835130691528,
-0.01826048642396927,
-1.412421464920044,
0.7152600884437561,
0.837177574634552,
-0.5936768054962158,
-0.42697256803512573,
0.036905691027641296,
-0.35643601417541504,
-0.4753079116344452,
-0.7347439527511597... |
javascript/reference/errors/string_literal_eol/index.md | JavaScript - Errors - String literal EOL - Examples - Multiple lines:
You can't split a string across multiple lines like this in JavaScript:
Example:
const longString = "This is a very long string which needs
to wrap across multiple lines because
otherwise my code is unreadab... | [
-1.461321473121643,
0.0865250751376152,
0.09795446693897247,
-0.02779620885848999,
0.051497042179107666,
-1.1128028631210327,
0.2610371708869934,
0.2062811702489853,
-0.8226272463798523,
0.1553274542093277,
-0.8028609752655029,
0.20176850259304047,
-0.14865222573280334,
-0.2214808166027069... |
javascript/reference/errors/property_access_denied/index.md | JavaScript - Errors - Property access denied:
The JavaScript exception "Permission denied to access property" occurs when there was an attempt to access an object for which you have no permission. | [
0.20958474278450012,
0.7233833074569702,
-0.8352850079536438,
-0.21604354679584503,
-0.8785306215286255,
-1.239758014678955,
0.8607218861579895,
0.7468452453613281,
-0.09343370050191879,
-0.377112478017807,
-0.629173994064331,
-0.781264066696167,
-1.3324837684631348,
-0.7820103764533997,
... |
javascript/reference/errors/property_access_denied/index.md | JavaScript - Errors - Property access denied - Message:
Example:
DOMException: Blocked a frame with origin "x" from accessing a cross-origin frame. (Chromium-based)
DOMException: Permission denied to access property "x" on cross-origin object (Firefox)
SecurityError: Blocked a frame with origin "x" from accessing a c... | [
0.8437572121620178,
-0.1314672976732254,
-1.1498820781707764,
-1.029443383216858,
-0.7784831523895264,
-0.9524762630462646,
0.6699053049087524,
0.6518607139587402,
-0.21382808685302734,
-0.0002264576032757759,
-0.07342582941055298,
-0.647405207157135,
-0.27449122071266174,
-1.0496993064880... |
javascript/reference/errors/property_access_denied/index.md | JavaScript - Errors - Property access denied - Error type:
`DOMException`. | [
0.3153459131717682,
-0.07829177379608154,
-0.39107075333595276,
-0.7107326984405518,
-1.0657696723937988,
-0.5651714205741882,
0.8438946008682251,
1.6188899278640747,
-0.18761181831359863,
-0.5941089987754822,
0.13646243512630463,
0.14351335167884827,
-0.9810853600502014,
-1.50841534137725... |
javascript/reference/errors/property_access_denied/index.md | JavaScript - Errors - Property access denied - What went wrong?:
There was attempt to access an object for which you have no permission. This is likely an `iframe` element loaded from a different domain for which you violated the same-origin policy. | [
0.41581422090530396,
0.2713712751865387,
-1.0922725200653076,
-0.5061365365982056,
-0.8228740692138672,
-0.49175581336021423,
0.38115981221199036,
1.121698021888733,
-0.3775938153266907,
0.028539426624774933,
-0.3229826092720032,
-0.49676477909088135,
-1.206002950668335,
-0.853903889656066... |
javascript/reference/errors/property_access_denied/index.md | JavaScript - Errors - Property access denied - Examples - No permission to access document:
Example:
<iframe id="myframe" src="http://www1.w3c-test.org/common/blank.html"></iframe>
Example:
console.log(frames[0].document);
// Error: Permission denied to access property "document" | [
-0.11872158199548721,
0.8667442798614502,
-0.4988156259059906,
-1.0463563203811646,
-0.3167729377746582,
-1.0566630363464355,
0.6854943633079529,
1.1654138565063477,
-0.38329166173934937,
-0.017033860087394714,
-0.49800965189933777,
-0.9308215975761414,
-0.34495487809181213,
-0.55106610059... |
javascript/reference/errors/regex_invalid_property_name/index.md | JavaScript - Errors - Regex invalid property name:
The JavaScript exception "invalid property name in regular expression" or "invalid class property name in regular expression" occurs when the `\p` and `\P` Unicode character class escapes are not followed by a valid Unicode property name and/or value. | [
-0.6340938210487366,
-0.14546555280685425,
-0.7866280674934387,
0.5880508422851562,
0.11086241900920868,
-0.9859866499900818,
0.9010754823684692,
0.5291167497634888,
-1.0071890354156494,
-0.8554860949516296,
-0.8421021103858948,
-0.3336062431335449,
-0.5458955764770508,
-1.1275625228881836... |
javascript/reference/errors/regex_invalid_property_name/index.md | JavaScript - Errors - Regex invalid property name - Message:
Example:
SyntaxError: Invalid regular expression: /\p{x}/u: Invalid property name (V8-based)
SyntaxError: Invalid regular expression: /[\p{x}]/u: Invalid property name in character class (V8-based)
SyntaxError: invalid property name in regular expression (F... | [
-0.3249208629131317,
0.29778391122817993,
-0.6630974411964417,
-0.0656883642077446,
0.14983156323432922,
-1.1709729433059692,
0.9796627163887024,
0.9308592677116394,
-0.29645439982414246,
0.13417352735996246,
-0.41069158911705017,
-0.06262466311454773,
-0.644778847694397,
-1.59413123130798... |
javascript/reference/errors/regex_invalid_property_name/index.md | JavaScript - Errors - Regex invalid property name - Error type:
`SyntaxError` | [
-0.04756941646337509,
0.710010826587677,
-0.011182880029082298,
-0.12182041257619858,
-0.8031809329986572,
-0.7981725335121155,
1.3456302881240845,
1.819298505783081,
-0.5528886914253235,
-1.185252070426941,
0.11383111029863358,
-0.40633851289749146,
-0.5922124981880188,
-0.877385258674621... |
javascript/reference/errors/regex_invalid_property_name/index.md | JavaScript - Errors - Regex invalid property name - What went wrong?:
In Unicode-aware mode, the `\p` and `\P` escape sequences are used to match characters or character sequences based on their Unicode properties. The `\p` escape sequence matches characters with the specified Unicode property, while the `\P` escape s... | [
-1.0983364582061768,
0.014280530624091625,
-0.6039979457855225,
0.5044943690299988,
0.18089763820171356,
-1.0589869022369385,
1.2637817859649658,
0.8852283954620361,
-0.3476200997829437,
-0.5532838106155396,
-0.8182371854782104,
0.18703877925872803,
-0.4366056025028229,
-0.8021952509880066... |
javascript/reference/errors/regex_invalid_property_name/index.md | JavaScript - Errors - Regex invalid property name - Examples - Invalid cases:
Example:
/\p{x}/u; // "x" is not a valid Unicode property name
/\p{Script=x}/u; // "x" is not a valid value for Script
/\property/u; // "\p" is not followed by the right syntax
/\p{RGI_Emoji_Flag_Sequence}/u;
// "RGI_Emoji_Flag_Sequence" is... | [
-0.6481948494911194,
0.4855373203754425,
-0.7699328064918518,
0.31481775641441345,
-0.17874492704868317,
-1.1358919143676758,
0.8847665786743164,
0.7514905333518982,
-0.6337776780128479,
-0.3518463969230652,
-0.2611393332481384,
-0.23194995522499084,
-0.21975500881671906,
-1.04902315139770... |
javascript/reference/errors/regex_invalid_property_name/index.md | JavaScript - Errors - Regex invalid property name - Examples - Valid cases:
Example:
/\p{Script=Latin}/u; // "Script=Latin" is a valid Unicode property
/\p{Letter}/u; // "Letter" is valid value for General_Category
/\p{RGI_Emoji_Flag_Sequence}/v; // Property of strings can only be used in "v" mode | [
-0.8053926229476929,
0.051222387701272964,
-0.2830350995063782,
0.48161816596984863,
0.4308715760707855,
-1.1451609134674072,
0.8461126685142517,
0.9971831440925598,
-0.501318097114563,
-0.42260080575942993,
-0.08212712407112122,
0.20251093804836273,
-0.4274810552597046,
-0.790690183639526... |
javascript/reference/errors/deprecated_source_map_pragma/index.md | JavaScript - Errors - Deprecated source map pragma:
The JavaScript warning "Using `//@` to indicate sourceURL pragmas is deprecated. Use `//#` instead" occurs when there is a deprecated source map syntax in a JavaScript source. | [
-1.1778087615966797,
0.47888079285621643,
-1.249158501625061,
-0.20186147093772888,
-0.7610618472099304,
-2.756359338760376,
0.4657016098499298,
1.270681381225586,
-0.3727598786354065,
0.396454393863678,
-0.35314273834228516,
-0.02489633299410343,
0.28826263546943665,
-0.766878604888916,
... |
javascript/reference/errors/deprecated_source_map_pragma/index.md | JavaScript - Errors - Deprecated source map pragma - Message:
Example:
Warning: SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead
Warning: SyntaxError: Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead | [
-1.3458565473556519,
0.5331257581710815,
-0.8263263702392578,
-0.2103070318698883,
-0.8164762258529663,
-2.9260783195495605,
0.4094984233379364,
1.4074634313583374,
-0.21643804013729095,
0.5499139428138733,
-0.15336082875728607,
0.22532673180103302,
0.373660147190094,
-0.5448633432388306,
... |
javascript/reference/errors/deprecated_source_map_pragma/index.md | JavaScript - Errors - Deprecated source map pragma - Error type:
A warning that a `SyntaxError` occurred. JavaScript execution won't be halted. | [
-0.03337347134947777,
0.36059504747390747,
-0.8368123769760132,
-0.24179016053676605,
-0.8779711723327637,
-1.3818519115447998,
1.1779783964157104,
2.156740188598633,
-0.3224050998687744,
-0.6813192963600159,
0.07904110103845596,
-0.4874546229839325,
0.004488914739340544,
-0.19297066330909... |
javascript/reference/errors/deprecated_source_map_pragma/index.md | JavaScript - Errors - Deprecated source map pragma - What went wrong?:
There is a deprecated source map syntax in a JavaScript source.
JavaScript sources are often combined and minified to make delivering them from the server more efficient. With source maps, the debugger can map the code being executed to the origin... | [
-0.812128484249115,
0.10147815942764282,
-0.7441381812095642,
-0.1357405185699463,
0.4132060706615448,
-2.2020249366760254,
0.6914187669754028,
1.0084534883499146,
-0.6370558738708496,
0.6625736951828003,
-0.43269720673561096,
-0.5558935403823853,
-0.3441053032875061,
-0.9303948283195496,
... |
javascript/reference/errors/deprecated_source_map_pragma/index.md | JavaScript - Errors - Deprecated source map pragma - Examples - Deprecated syntax:
Syntax with the "@" sign is deprecated.
Example:
//@ sourceMappingURL=http://example.com/path/to/your/sourcemap.map | [
-1.197411060333252,
0.1679104119539261,
-0.4370861053466797,
-0.45172441005706787,
-0.29404714703559875,
-2.8158490657806396,
0.7499009966850281,
0.9887656569480896,
-0.2761997878551483,
0.2642126977443695,
0.40330129861831665,
0.23026041686534882,
0.20133255422115326,
-0.94609534740448,
... |
javascript/reference/errors/deprecated_source_map_pragma/index.md | JavaScript - Errors - Deprecated source map pragma - Examples - Standard syntax:
Use the "#" sign instead.
Example:
//# sourceMappingURL=http://example.com/path/to/your/sourcemap.map
Or, alternatively, you can set a `SourceMap` header to your JavaScript file to avoid having a comment at all:
Example:
SourceMap: /... | [
-1.2255617380142212,
-0.6287049055099487,
-0.7856413125991821,
0.10353348404169083,
-0.10605303943157196,
-2.48058819770813,
0.360355019569397,
0.8670557141304016,
-0.3433038592338562,
-0.5628294348716736,
0.10807374119758606,
0.2983269691467285,
0.16852767765522003,
-0.9926739931106567,
... |
javascript/reference/errors/cant_use_nullish_coalescing_unparenthesized/index.md | JavaScript - Errors - Cant use nullish coalescing unparenthesized:
The JavaScript exception "cannot use `??` unparenthesized within `||` and `&&` expressions" occurs when a nullish coalescing operator is used with a logical OR or logical AND in the same expression without parentheses. | [
-0.39178359508514404,
1.2981075048446655,
-0.11224368214607239,
0.9739461541175842,
-1.1627774238586426,
-1.2859761714935303,
0.4412224292755127,
1.4258836507797241,
-0.5120978951454163,
0.6884816288948059,
-0.14076738059520721,
-0.6817039847373962,
1.0530060529708862,
-0.7434784173965454,... |
javascript/reference/errors/cant_use_nullish_coalescing_unparenthesized/index.md | JavaScript - Errors - Cant use nullish coalescing unparenthesized - Message:
Example:
SyntaxError: Unexpected token '??' (V8-based)
SyntaxError: cannot use `??` unparenthesized within `||` and `&&` expressions (Firefox)
SyntaxError: Unexpected token '??'. Coalescing and logical operators used together in the same exp... | [
-0.7727294564247131,
1.1622164249420166,
-0.8181903958320618,
0.46125277876853943,
-1.0387897491455078,
-1.2296911478042603,
0.7769260406494141,
1.498795509338379,
-0.15652653574943542,
0.2584969997406006,
0.29987362027168274,
-0.1796165108680725,
0.78886878490448,
-0.7319357991218567,
-... |
javascript/reference/errors/cant_use_nullish_coalescing_unparenthesized/index.md | JavaScript - Errors - Cant use nullish coalescing unparenthesized - Error type:
`SyntaxError` | [
-0.3382055461406708,
1.4098626375198364,
-0.19953051209449768,
0.007731093093752861,
-1.5174599885940552,
-0.8389106392860413,
1.1319864988327026,
2.537776231765747,
-0.45570382475852966,
0.09254343807697296,
0.5365325212478638,
-0.4442569315433502,
0.5062310099601746,
-0.2985113263130188,... |
javascript/reference/errors/cant_use_nullish_coalescing_unparenthesized/index.md | JavaScript - Errors - Cant use nullish coalescing unparenthesized - What went wrong?:
The operator precedence chain looks like this:
Example:
| > && > || > =
| > ?? > =
However, the precedence between `??` and `&&`/`||` is intentionally undefined, because the short circuiting behavior of logical... | [
-0.30804896354675293,
1.3398592472076416,
-0.6835233569145203,
0.23631449043750763,
-0.2615665793418884,
-0.837787926197052,
1.050927996635437,
1.644076943397522,
-0.5436245799064636,
1.171346664428711,
-0.3849027156829834,
-1.2679920196533203,
1.0181294679641724,
-0.6087089776992798,
-0... |
javascript/reference/errors/cant_use_nullish_coalescing_unparenthesized/index.md | JavaScript - Errors - Cant use nullish coalescing unparenthesized - Examples:
When migrating legacy code that uses `||` and `&&` for guarding against `null` or `undefined`, you may often convert it partially:
Example:
function getId(user, fallback) {
// Previously: user && user.id || fallback
return user && user... | [
-0.8861775994300842,
1.655511498451233,
-0.8712724447250366,
0.4463522732257843,
-0.7609328031539917,
-1.2741119861602783,
1.3021918535232544,
1.492641568183899,
-0.8060046434402466,
1.2645022869110107,
-0.2929515838623047,
-0.5957288146018982,
0.0680481418967247,
-0.19372528791427612,
-... |
javascript/reference/errors/cant_delete_private_fields/index.md | JavaScript - Errors - Cant delete private fields:
The JavaScript exception "SyntaxError: private fields can't be deleted" occurs when `delete` is used on a private element of a class or an object. | [
-0.5672028660774231,
0.2439628392457962,
-0.776278018951416,
-0.01832151971757412,
-0.48806649446487427,
-1.8804069757461548,
1.769205927848816,
0.9710432887077332,
0.05885491147637367,
-0.8263642191886902,
-0.17339695990085602,
-0.24563173949718475,
-1.0245946645736694,
-0.010843953117728... |
javascript/reference/errors/cant_delete_private_fields/index.md | JavaScript - Errors - Cant delete private fields - Message:
Example:
SyntaxError: Private fields can not be deleted (V8-based)
SyntaxError: private fields can't be deleted (Firefox)
SyntaxError: Cannot delete private field X (Safari) | [
-0.9720311760902405,
0.3102802038192749,
-1.242409586906433,
-0.597145676612854,
-0.9326576590538025,
-1.555653691291809,
1.6626676321029663,
1.060373067855835,
0.44357380270957947,
-0.8433818221092224,
0.25423353910446167,
-0.18943926692008972,
-0.8236983418464661,
-0.2605004608631134,
... |
javascript/reference/errors/cant_delete_private_fields/index.md | JavaScript - Errors - Cant delete private fields - Error type:
`SyntaxError` | [
-0.7295042276382446,
0.4115689992904663,
-0.36519545316696167,
-0.20086248219013214,
-0.7262566685676575,
-1.2767561674118042,
1.8139123916625977,
1.8144457340240479,
-0.019095193594694138,
-0.8755813837051392,
0.6488155126571655,
0.17450161278247833,
-0.9275914430618286,
-0.13107687234878... |
javascript/reference/errors/cant_delete_private_fields/index.md | JavaScript - Errors - Cant delete private fields - What went wrong?:
There's code trying to `delete` a private element (field or method) of an object or a class. This is forbidden by JavaScript—private elements cannot be added or removed on the fly. | [
-0.7859446406364441,
0.16641804575920105,
-0.9188026785850525,
-0.6004748344421387,
-0.33781698346138,
-1.991806149482727,
1.0641769170761108,
0.9709958434104919,
-0.5031511187553406,
-0.5988451242446899,
-0.4861934185028076,
-0.40971559286117554,
-1.1770989894866943,
-0.25559842586517334,... |
javascript/reference/errors/cant_delete_private_fields/index.md | JavaScript - Errors - Cant delete private fields - Examples:
Example:
class MyClass {
#myPrivateField;
deleteIt() {
delete this.#myPrivateField; // SyntaxError: private fields can't be deleted
}
}
Example:
class MyClass {
#myPrivateMethod() {
}
#deleteIt() {
delete this.#myPrivateMethod; // Synt... | [
-1.2513012886047363,
-0.028935745358467102,
-0.4016558825969696,
-0.3730699419975281,
-0.5744450688362122,
-1.9005197286605835,
1.1909388303756714,
1.290043592453003,
0.33129584789276123,
-0.5686997771263123,
-0.10010320693254471,
-0.22666895389556885,
-1.061565637588501,
-0.51926672458648... |
javascript/reference/errors/deprecated_octal_literal/index.md | JavaScript - Errors - Deprecated octal literal:
The JavaScript strict mode-only exception "0-prefixed octal literals are deprecated; use the "0o" prefix instead" occurs when deprecated octal literals (`0` followed by digits) are used. | [
-1.156018614768982,
0.1801283210515976,
-0.48935666680336,
-0.4142031669616699,
-0.21218456327915192,
-1.570771336555481,
1.369173288345337,
0.8539498448371887,
-0.6771711111068726,
-0.3781968057155609,
-1.2178057432174683,
-0.8589475154876709,
-0.1926744431257248,
-0.7128074169158936,
0... |
javascript/reference/errors/deprecated_octal_literal/index.md | JavaScript - Errors - Deprecated octal literal - Message:
Example:
SyntaxError: Octal literals are not allowed in strict mode. (V8-based)
SyntaxError: Decimals with leading zeros are not allowed in strict mode. (V8-based)
SyntaxError: Unexpected number (V8-based)
SyntaxError: "0"-prefixed octal literals are deprecate... | [
-0.7304712533950806,
0.04420653358101845,
-0.5970385074615479,
0.12748843431472778,
0.34521663188934326,
-1.0808098316192627,
1.016239047050476,
1.1384501457214355,
0.1093524619936943,
-0.07963753491640091,
-0.4272351861000061,
0.09328915178775787,
0.08373535424470901,
-0.33371713757514954... |
javascript/reference/errors/deprecated_octal_literal/index.md | JavaScript - Errors - Deprecated octal literal - Error type:
`SyntaxError` in strict mode only. | [
-1.0412760972976685,
0.46148303151130676,
-0.5762643814086914,
-0.819800078868866,
-0.40920063853263855,
-1.0057555437088013,
1.4107669591903687,
1.7499204874038696,
-0.12016917765140533,
-0.45476025342941284,
-0.2790142893791199,
-0.9937708973884583,
-0.02082483470439911,
-0.0875701159238... |
javascript/reference/errors/deprecated_octal_literal/index.md | JavaScript - Errors - Deprecated octal literal - What went wrong?:
Octal literals are deprecated. When you prefix a decimal integer with `0`, you actually change it to an octal literal, which may be surprising. The standardized syntax uses a leading zero followed by a lowercase or uppercase Latin letter "O" (`0o` or `... | [
-1.487902045249939,
0.5719006061553955,
-0.7586212158203125,
-0.8174962997436523,
-0.006539314053952694,
-1.8179302215576172,
0.9703333377838135,
0.9456884264945984,
-0.6288998126983643,
-0.25903525948524475,
-1.1179758310317993,
-0.36951884627342224,
-0.44038262963294983,
-0.6075001358985... |
javascript/reference/errors/deprecated_octal_literal/index.md | JavaScript - Errors - Deprecated octal literal - Examples - "0"-prefixed octal literals:
Example:
"use strict";
03;
// SyntaxError: "0"-prefixed octal literals are deprecated; use the "0o" prefix instead | [
-1.1854891777038574,
0.5927353501319885,
-0.5775595307350159,
-1.0319716930389404,
0.02231251448392868,
-1.791763424873352,
1.6916923522949219,
1.0487945079803467,
-0.4082111716270447,
-0.26385951042175293,
-0.9820204377174377,
-0.6958053708076477,
-0.0038444034289568663,
-0.79184186458587... |
javascript/reference/errors/deprecated_octal_literal/index.md | JavaScript - Errors - Deprecated octal literal - Examples - Valid octal numbers:
Use a leading zero followed by the letter "o" or "O":
Example:
0o3; | [
-0.7891758680343628,
0.5881233215332031,
-1.2373696565628052,
-1.1167532205581665,
-0.32539641857147217,
-1.513550043106079,
1.2774262428283691,
0.0512549951672554,
-1.208046793937683,
-0.43852484226226807,
-0.8423242568969727,
-0.6484383344650269,
-0.09936448186635971,
-0.5836288332939148... |
javascript/reference/errors/missing_bracket_after_list/index.md | JavaScript - Errors - Missing bracket after list:
The JavaScript exception "missing ] after element list" occurs when there is an error with the array initializer syntax somewhere. Likely there is a closing square bracket (`]`) or a comma (`,`) missing. | [
-0.31668370962142944,
-0.6869657039642334,
-0.396138072013855,
0.26245519518852234,
0.35223373770713806,
-1.3138562440872192,
0.7958984375,
0.9322835803031921,
-1.124112844467163,
-0.12710388004779816,
0.3433936536312103,
-0.6929922103881836,
-0.8200089931488037,
-0.05552927404642105,
-0... |
javascript/reference/errors/missing_bracket_after_list/index.md | JavaScript - Errors - Missing bracket after list - Message:
Example:
SyntaxError: missing ] after element list (Firefox)
SyntaxError: Unexpected token ';'. Expected either a closing ']' or a ',' following an array element. (Safari) | [
-0.7789420485496521,
-0.6233496069908142,
-0.6119850873947144,
-0.3561994731426239,
-0.16904327273368835,
-1.3135994672775269,
1.153471827507019,
0.7925002574920654,
-0.8468912243843079,
-0.39902839064598083,
1.0355560779571533,
-0.17849865555763245,
-0.5200856328010559,
-0.266724437475204... |
javascript/reference/errors/missing_bracket_after_list/index.md | JavaScript - Errors - Missing bracket after list - Error type:
`SyntaxError`. | [
-0.4167294204235077,
-0.5379751324653625,
-0.4785514175891876,
-0.47217682003974915,
-0.2667411267757416,
-0.6454623937606812,
1.089680552482605,
1.734134316444397,
-0.6222381591796875,
-1.0930489301681519,
0.7955513596534729,
-0.24144543707370758,
-0.7202281355857849,
-0.229131281375885,
... |
javascript/reference/errors/missing_bracket_after_list/index.md | JavaScript - Errors - Missing bracket after list - What went wrong?:
There is an error with the array initializer syntax somewhere. Likely there is a closing square bracket (`]`) or a comma (`,`) missing. | [
-0.249337300658226,
0.04201527684926987,
-0.8648900389671326,
-0.5639818906784058,
0.09781231731176376,
-1.0034807920455933,
0.2760154902935028,
1.8087644577026367,
-0.7476877570152283,
-0.3714199662208557,
0.512707531452179,
-0.7487932443618774,
-0.3947656750679016,
-0.21192744374275208,
... |
javascript/reference/errors/missing_bracket_after_list/index.md | JavaScript - Errors - Missing bracket after list - Examples - Incomplete array initializer:
Example:
const list = [1, 2,
const instruments = [
"Ukulele",
"Guitar",
"Piano",
};
const data = [{ foo: "bar" } { bar: "foo" }];
Correct would be:
Example:
const list = [1, 2];
const instruments = ["Ukulele", "Gui... | [
0.4499838948249817,
0.07344923168420792,
-2.096545696258545,
0.40740320086479187,
0.18864700198173523,
-1.2174651622772217,
1.1489657163619995,
0.3296979069709778,
-0.6197195649147034,
0.6244370341300964,
0.6669626832008362,
0.058099813759326935,
-0.23726029694080353,
-0.2262946218252182,
... |
javascript/reference/errors/regex_negated_char_class_with_strings/index.md | JavaScript - Errors - Regex negated char class with strings:
The JavaScript exception "negated character class with strings in regular expression" occurs when a `v`-mode character class is negated and may be able to match a string (more than one character). | [
-0.7671701312065125,
-0.8497340679168701,
0.1443081498146057,
-0.03214239329099655,
0.5340549945831299,
-1.18108069896698,
0.5761480331420898,
0.9287254810333252,
-0.4785730242729187,
-0.3734441101551056,
-0.3303764760494232,
-1.3284707069396973,
-0.777838945388794,
-0.6022710204124451,
... |
javascript/reference/errors/regex_negated_char_class_with_strings/index.md | JavaScript - Errors - Regex negated char class with strings - Message:
Example:
SyntaxError: Invalid regular expression: /[^\p{RGI_Emoji_Flag_Sequence}]/v: Negated character class may contain strings (V8-based)
SyntaxError: negated character class with strings in regular expression (Firefox)
SyntaxError: Invalid regu... | [
-1.47078537940979,
-0.43565037846565247,
0.2977971136569977,
-0.579566240310669,
0.10551285743713379,
-1.6198846101760864,
0.7119192481040955,
1.0841825008392334,
-0.302742600440979,
0.0762348622083664,
-0.04243586212396622,
-0.8801742792129517,
-0.5692441463470459,
-0.7211875915527344,
... |
javascript/reference/errors/regex_negated_char_class_with_strings/index.md | JavaScript - Errors - Regex negated char class with strings - Error type:
`SyntaxError` | [
-0.9197715520858765,
0.37956082820892334,
0.8532459139823914,
-0.9197101593017578,
-0.17093031108379364,
-1.6131776571273804,
0.9476913809776306,
1.9434987306594849,
-0.3379281461238861,
-0.6279709935188293,
0.41093167662620544,
-0.8046739101409912,
-0.861175000667572,
-0.2317148894071579,... |
javascript/reference/errors/regex_negated_char_class_with_strings/index.md | JavaScript - Errors - Regex negated char class with strings - What went wrong?:
In `v` mode, character classes are able to match more than 1 character. For example, `/[\q{abc}]/v` would match the sequence `"abc"`, and `/[\p{RGI_Emoji_Flag_Sequence}]/v` would match any character sequence that represents an emoji flag. ... | [
-0.9097151160240173,
-0.8646894097328186,
0.5986399054527283,
-0.6172058582305908,
0.5878474712371826,
-1.3351445198059082,
0.4581843316555023,
0.5307745933532715,
-0.09526420384645462,
-0.13187898695468903,
0.1637674868106842,
-1.0054492950439453,
-0.24832676351070404,
-0.6596105694770813... |
javascript/reference/errors/regex_negated_char_class_with_strings/index.md | JavaScript - Errors - Regex negated char class with strings - Examples - Invalid cases:
Example:
/[^\p{RGI_Emoji_Flag_Sequence}]/v; | [
-1.2441987991333008,
-0.1766124814748764,
0.46398743987083435,
-0.7286513447761536,
-0.11625061929225922,
-1.359964370727539,
0.45364031195640564,
1.0267558097839355,
-0.8116039037704468,
-0.3378000557422638,
-0.01692161336541176,
-1.2258179187774658,
-0.3534945845603943,
-0.45272937417030... |
javascript/reference/errors/regex_negated_char_class_with_strings/index.md | JavaScript - Errors - Regex negated char class with strings - Examples - Valid cases:
Example:
// Matches two characters that are not an emoji flag sequence
/(?!\p{RGI_Emoji_Flag_Sequence})../v; | [
-0.7866154909133911,
-0.14625109732151031,
0.3283912241458893,
-0.48576322197914124,
0.023187175393104553,
-1.5071616172790527,
0.7696382999420166,
0.7894395589828491,
-0.6503264904022217,
-0.3812884986400604,
-0.11862286180257797,
-1.4061856269836426,
-0.18620961904525757,
-0.604426383972... |
javascript/reference/errors/either_be_both_static_or_non-static/index.md | JavaScript - Errors - Either be both static or non-static:
The JavaScript exception "mismatched placement" occurs when a private getter and setter are mismatched in whether or not they are `static`. | [
-0.3302328884601593,
-1.4073290824890137,
-1.4580785036087036,
0.469513863325119,
0.1453445851802826,
-0.6685175895690918,
0.7668352723121643,
0.6590319275856018,
-0.031155278906226158,
0.25582602620124817,
-0.17177855968475342,
-1.0610042810440063,
-0.14217820763587952,
-0.945561468601226... |
javascript/reference/errors/either_be_both_static_or_non-static/index.md | JavaScript - Errors - Either be both static or non-static - Message:
Example:
SyntaxError: Identifier '#x' has already been declared (V8-based)
SyntaxError: getter and setter for private name #x should either be both static or non-static (Firefox)
SyntaxError: Cannot declare a private non-static getter if there is a ... | [
-0.6433064341545105,
-0.181492879986763,
-1.3742706775665283,
0.3333812355995178,
-0.5841511487960815,
-1.345951795578003,
0.8045215606689453,
1.3497731685638428,
0.6018815040588379,
0.2227860987186432,
0.39122793078422546,
-0.3892475366592407,
-0.31140726804733276,
-1.414117455482483,
-... |
javascript/reference/errors/either_be_both_static_or_non-static/index.md | JavaScript - Errors - Either be both static or non-static - Error type:
`SyntaxError` | [
-0.043779388070106506,
-0.31462669372558594,
-0.04632401838898659,
0.3505589962005615,
-0.034962233155965805,
-0.7527704834938049,
0.8297374844551086,
2.4491806030273438,
0.4950435161590576,
-0.5980191826820374,
0.038401249796152115,
-0.3497932255268097,
0.14239944517612457,
-0.38827663660... |
javascript/reference/errors/either_be_both_static_or_non-static/index.md | JavaScript - Errors - Either be both static or non-static - What went wrong?:
Private getters and setters for the same name must either be both `static`, or both non-static. This limitation does not exist for public methods. | [
-0.4098286032676697,
-0.3400299847126007,
-1.7427424192428589,
0.44223326444625854,
0.08094499260187149,
-1.053134560585022,
-0.2637050747871399,
0.9444435238838196,
-0.34528830647468567,
0.3213447630405426,
-0.21684318780899048,
-0.4833987057209015,
-0.3076409101486206,
-1.733217000961303... |
javascript/reference/errors/either_be_both_static_or_non-static/index.md | JavaScript - Errors - Either be both static or non-static - Examples - Mismatched placement:
Example:
class Test {
static set #foo(_) {}
get #foo() {}
}
// SyntaxError: getter and setter for private name #foo should either be both static or non-static
Since `foo` is private, the methods must be either both `sta... | [
-0.3935794532299042,
-0.6142963767051697,
-1.1875157356262207,
0.07353571057319641,
0.18561872839927673,
-1.3055341243743896,
0.8625385761260986,
1.299763798713684,
-0.18173947930335999,
0.418155312538147,
0.203863725066185,
-0.4496016502380371,
-0.21758407354354858,
-1.3152008056640625,
... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor:
The JavaScript exception "is not a constructor" occurs when there was an attempt to use an object or a variable as a constructor, but that object or variable is not a constructor. | [
-0.04851199686527252,
-0.3931970000267029,
-0.8841992616653442,
0.8664164543151855,
-0.6402597427368164,
-1.4683183431625366,
0.15922990441322327,
1.3922549486160278,
-0.8522307872772217,
-0.34506872296333313,
-0.36501532793045044,
-1.5662024021148682,
-0.3280292749404907,
-0.4928936362266... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor - Message:
Example:
TypeError: x is not a constructor (V8-based & Firefox & Safari) | [
-0.1418667584657669,
-0.08381455391645432,
-1.5463067293167114,
0.03390919417142868,
-1.2533113956451416,
-0.19207920134067535,
0.19385534524917603,
1.549739956855774,
-0.32079434394836426,
-0.4952342212200165,
0.507086992263794,
-1.060075044631958,
-0.2390405535697937,
-0.9080944061279297... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor - Error type:
`TypeError` | [
-0.2836747467517853,
-0.05885756388306618,
-1.0858231782913208,
-0.40169963240623474,
-0.8537857532501221,
-0.06111105903983116,
0.32342442870140076,
1.9625604152679443,
-0.6986090540885925,
-0.46786320209503174,
0.27983754873275757,
-0.9695782661437988,
0.04105998948216438,
-0.53588706254... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor - What went wrong?:
There was an attempt to use an object or a variable as a constructor, but that object or variable is not a constructor. See constructor or the `new` operator for more information on what a constructor is.
There are many global objects, like `String` or `Arra... | [
-0.7100240588188171,
-0.2516753673553467,
-0.9340832829475403,
0.8134889006614685,
0.11983006447553635,
-1.9218049049377441,
-0.4117982089519501,
1.2533693313598633,
-0.665682852268219,
-0.005198377184569836,
-0.261984646320343,
-0.6730707287788391,
-0.236243337392807,
-0.2749902904033661,... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor - Examples - Invalid cases:
Example:
const Car = 1;
new Car();
// TypeError: Car is not a constructor
new Math();
// TypeError: Math is not a constructor
new Symbol();
// TypeError: Symbol is not a constructor
function* f() {}
const obj = new f();
// TypeError: f is not a co... | [
0.009301959536969662,
-0.7350981831550598,
-0.8862231969833374,
0.3321632742881775,
-0.26040083169937134,
-1.0638436079025269,
-0.30672910809516907,
1.8228341341018677,
-0.15410108864307404,
0.1533297896385193,
-0.11385153979063034,
-0.4683932065963745,
0.1933285892009735,
-0.4412814378738... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor - Examples - A car constructor:
Suppose you want to create an object type for cars. You want this type of object to be called `Car`, and you want it to have properties for make, model, and year. To do this, you would write the following function:
Example:
function Car(make, mo... | [
-0.684088408946991,
-0.8532505631446838,
-0.5376043915748596,
0.8720700740814209,
0.15927782654762268,
-1.559391736984253,
-0.6761857271194458,
0.8930134773254395,
-0.5732014775276184,
0.3512890040874481,
0.5103636980056763,
-0.25583240389823914,
-0.30085185170173645,
-0.27008089423179626,... |
javascript/reference/errors/not_a_constructor/index.md | JavaScript - Errors - Not a constructor - Examples - In Promises:
When returning an immediately-resolved or immediately-rejected Promise, you do not need to create a `new Promise(...)` and act on it. Instead, use the `Promise.resolve()` or `Promise.reject()` static methods.
This is not legal (the `Promise` constructo... | [
-0.3712298274040222,
0.5366645455360413,
-0.19987091422080994,
-0.2594298720359802,
-0.43143200874328613,
-1.080444574356079,
0.4659954011440277,
1.5717414617538452,
-0.728137195110321,
0.5255429744720459,
-0.5427829027175903,
-0.2781940996646881,
-0.011169897392392159,
0.38136932253837585... |
javascript/reference/errors/regex_invalid_identity_escape/index.md | JavaScript - Errors - Regex invalid identity escape:
The JavaScript exception "invalid identity escape in regular expression" occurs when a Unicode-aware regular expression pattern contains an escape sequence that does not represent a recognized escape sequence. | [
-0.3304945230484009,
0.31368717551231384,
-0.8537081480026245,
0.43944042921066284,
-0.186570942401886,
-0.6992993354797363,
0.6010092496871948,
0.5349740982055664,
-0.5190033316612244,
-0.3648872673511505,
-1.0810195207595825,
-1.4168410301208496,
-0.4960487484931946,
-0.21557269990444183... |
javascript/reference/errors/regex_invalid_identity_escape/index.md | JavaScript - Errors - Regex invalid identity escape - Message:
Example:
SyntaxError: Invalid regular expression: /\q/u: Invalid escape (V8-based)
SyntaxError: invalid identity escape in regular expression (Firefox)
SyntaxError: Invalid regular expression: invalid escaped character for Unicode pattern (Safari) | [
-0.48317041993141174,
0.590545117855072,
-0.8151041865348816,
-0.8741716146469116,
-0.009345832280814648,
-0.9641454815864563,
1.0689787864685059,
0.5676525235176086,
-0.5387835502624512,
-0.0226710494607687,
0.02925976924598217,
-0.9609368443489075,
-0.34482064843177795,
-0.77304869890213... |
javascript/reference/errors/regex_invalid_identity_escape/index.md | JavaScript - Errors - Regex invalid identity escape - Error type:
`SyntaxError` | [
-0.036639921367168427,
0.3647726774215698,
-0.19325819611549377,
-0.4426964521408081,
-0.8851523399353027,
-0.5550516247749329,
1.21399986743927,
1.5774511098861694,
-0.13395023345947266,
-0.9487884640693665,
0.04957148805260658,
-0.784656286239624,
-0.5341816544532776,
-0.1037544608116149... |
javascript/reference/errors/regex_invalid_identity_escape/index.md | JavaScript - Errors - Regex invalid identity escape - What went wrong?:
In Unicode-unaware mode, `\` could be used to escape any character, including those without a defined meaning. In these cases, the escaped character represents itself. For example, `\q` would match the character `q`. This severely limits the abili... | [
-0.8259122371673584,
0.4311346709728241,
-1.0669715404510498,
-0.3046676516532898,
-0.149294912815094,
-0.4068450927734375,
1.1258033514022827,
1.0105284452438354,
-0.07908163964748383,
-0.21056094765663147,
-0.1292586773633957,
-0.5794462561607361,
-0.11825034022331238,
-0.132122948765754... |
javascript/reference/errors/regex_invalid_identity_escape/index.md | JavaScript - Errors - Regex invalid identity escape - Examples - Invalid cases:
Example:
/[\f\v\n\t\ ]/u; | [
0.27282461524009705,
0.30456677079200745,
-0.9367778897285461,
-0.22943051159381866,
-0.12485605478286743,
0.03778265789151192,
0.8931791186332703,
0.8627973198890686,
-0.6690940856933594,
-0.18890924751758575,
-0.11694677174091339,
-1.123060703277588,
-0.7908477187156677,
-0.3555973470211... |
javascript/reference/errors/regex_invalid_identity_escape/index.md | JavaScript - Errors - Regex invalid identity escape - Examples - Valid cases:
Example:
// There's no need to escape the space
/[\f\v\n\t ]/u; | [
0.1794755458831787,
0.5090821981430054,
-0.9469238519668579,
-0.3620174825191498,
-0.2841370105743408,
-0.1512366384267807,
0.6188582181930542,
-0.294534832239151,
-0.11859019100666046,
-0.24079176783561707,
-0.10205802321434021,
-1.5442091226577759,
-1.1679716110229492,
-0.236140951514244... |
javascript/reference/errors/malformed_uri/index.md | JavaScript - Errors - Malformed URI:
The JavaScript exception "malformed URI sequence" occurs when URI encoding or decoding wasn't successful. | [
-0.08839131146669388,
0.25299519300460815,
-0.5890523791313171,
-0.20418134331703186,
-0.8885841965675354,
-0.06586269289255142,
0.33808696269989014,
0.7710774540901184,
-1.4089806079864502,
-0.2634689211845398,
-1.1444262266159058,
-1.4524831771850586,
0.1503637582063675,
-0.7250419259071... |
javascript/reference/errors/malformed_uri/index.md | JavaScript - Errors - Malformed URI - Message:
Example:
URIError: URI malformed (V8-based)
URIError: malformed URI sequence (Firefox)
URIError: String contained an illegal UTF-16 sequence. (Safari) | [
-0.5540112853050232,
0.2564769387245178,
-1.0481821298599243,
-0.4755827784538269,
-0.8639155626296997,
-0.10793730616569519,
0.8187693953514099,
1.059415340423584,
-1.1075204610824585,
-0.09959661960601807,
-0.4246620833873749,
-0.5852659344673157,
-0.3776557445526123,
-1.2314321994781494... |
javascript/reference/errors/malformed_uri/index.md | JavaScript - Errors - Malformed URI - Error type:
`URIError` | [
0.10655228793621063,
0.11202351003885269,
-0.8674495220184326,
-0.36518874764442444,
-1.3636901378631592,
0.6650558710098267,
1.2516846656799316,
1.5188262462615967,
-1.1516451835632324,
-0.9744117259979248,
-0.5117831826210022,
-0.8277574777603149,
-0.15831711888313293,
-0.688737928867340... |
javascript/reference/errors/malformed_uri/index.md | JavaScript - Errors - Malformed URI - What went wrong?:
URI encoding or decoding wasn't successful. An argument given to either the `decodeURI`, `encodeURI`, `encodeURIComponent`, or `decodeURIComponent` function was not valid, so that the function was unable encode or decode properly. | [
0.7002182006835938,
0.77278071641922,
-0.6758588552474976,
-0.7788655161857605,
-1.0306087732315063,
-0.6366868019104004,
0.10370071977376938,
0.9116642475128174,
-0.8645529747009277,
-0.24885843694210052,
-0.7800502777099609,
-1.2162318229675293,
0.43708741664886475,
-0.5807771682739258,
... |
javascript/reference/errors/malformed_uri/index.md | JavaScript - Errors - Malformed URI - Examples - Encoding:
Encoding replaces each instance of certain characters by one, two, three, or four escape sequences representing the UTF-8 encoding of the character. An `URIError` will be thrown if there is an attempt to encode a surrogate which is not part of a high-low pair,... | [
-0.2727518081665039,
0.2851010262966156,
-0.8613566160202026,
-0.009286102838814259,
-0.1851670742034912,
0.17450858652591705,
0.7127661108970642,
0.9367013573646545,
-1.2848169803619385,
-0.9283776879310608,
-0.9188511371612549,
-0.4628821313381195,
0.36338990926742554,
-0.298842936754226... |
javascript/reference/errors/malformed_uri/index.md | JavaScript - Errors - Malformed URI - Examples - Decoding:
Decoding replaces each escape sequence in the encoded URI component with the character that it represents. If there isn't such a character, an error will be thrown:
Example:
decodeURIComponent("%E0%A4%A");
// "URIError: malformed URI sequence"
With proper i... | [
-0.09787735342979431,
-0.10266207903623581,
-0.6797885298728943,
-0.03067069500684738,
-0.27412018179893494,
-0.16429546475410461,
0.9953168034553528,
0.4129835069179535,
-1.008825659751892,
-0.552262544631958,
-0.3535895049571991,
-1.064108967781067,
0.162869393825531,
0.04288853704929352... |
javascript/reference/errors/regex_duplicate_capture_group_name/index.md | JavaScript - Errors - Regex duplicate capture group name:
The JavaScript exception "duplicate capture group name in regular expression" occurs when a regular expression pattern contains two or more named capturing groups with the same name, and these capture groups could be matched at the same time. | [
-0.2594606280326843,
0.051840733736753464,
-1.625959038734436,
0.676531970500946,
-1.0797221660614014,
-0.23318198323249817,
0.769816517829895,
0.5559230446815491,
-1.5812909603118896,
-0.6835940480232239,
-1.2967015504837036,
-1.4362136125564575,
-0.5557436347007751,
-0.5631919503211975,
... |
javascript/reference/errors/regex_duplicate_capture_group_name/index.md | JavaScript - Errors - Regex duplicate capture group name - Message:
Example:
SyntaxError: Invalid regular expression: /(?<a>)(?<a>)/: Duplicate capture group name (V8-based)
SyntaxError: duplicate capture group name in regular expression (Firefox)
SyntaxError: Invalid regular expression: duplicate group specifier nam... | [
-0.6871755719184875,
0.5884435176849365,
-1.4731112718582153,
-0.09251554310321808,
-1.1061477661132812,
-0.9130816459655762,
1.1723856925964355,
0.6197633147239685,
-1.0558329820632935,
-0.281490683555603,
-0.33779892325401306,
-0.8523851633071899,
-0.2565673589706421,
-1.1224762201309204... |
javascript/reference/errors/regex_duplicate_capture_group_name/index.md | JavaScript - Errors - Regex duplicate capture group name - Error type:
`SyntaxError` | [
-0.41465628147125244,
0.3032008409500122,
-0.8713717460632324,
-0.3533446490764618,
-1.546419382095337,
-0.3774784505367279,
0.9172935485839844,
1.7580171823501587,
-0.9734045267105103,
-1.1090242862701416,
-0.09303954243659973,
-0.8045986294746399,
-0.4286811649799347,
-0.1811776310205459... |
javascript/reference/errors/regex_duplicate_capture_group_name/index.md | JavaScript - Errors - Regex duplicate capture group name - What went wrong?:
All named capturing groups in a regular expression pattern must have unique names. A more recent feature allows named capturing groups to share names, as long as they belong to different disjunction alternatives and cannot be matched at the s... | [
-0.48888063430786133,
-0.16658227145671844,
-1.4834781885147095,
0.28431546688079834,
-0.9863043427467346,
-0.9197478890419006,
1.2225227355957031,
-0.12339410930871964,
-1.414734125137329,
-0.2687920033931732,
-1.1534206867218018,
-1.8439927101135254,
-0.9768678545951843,
-0.3898149728775... |
javascript/reference/errors/regex_duplicate_capture_group_name/index.md | JavaScript - Errors - Regex duplicate capture group name - Examples - Invalid cases:
Example:
/(?<name>\w+) (?<name>\w+)/; | [
-0.27689769864082336,
0.6711037158966064,
-1.4175986051559448,
0.20718097686767578,
-1.137198805809021,
-0.10282473266124725,
1.0545464754104614,
1.013992190361023,
-1.8962831497192383,
-0.6188746690750122,
-0.20770543813705444,
-0.4865597188472748,
-0.5384371876716614,
-1.092787265777588,... |
javascript/reference/errors/regex_duplicate_capture_group_name/index.md | JavaScript - Errors - Regex duplicate capture group name - Examples - Valid cases:
Example:
/(?<firstName>\w+) (?<lastName>\w+)/;
/(?<year>\d{4})-\d{2}|\d{2}-(?<year>\d{4})/; | [
-0.22827014327049255,
0.9296625852584839,
-1.2771022319793701,
-0.1694166213274002,
-1.043949007987976,
0.14789238572120667,
1.0885916948318481,
0.8669518232345581,
-1.9109160900115967,
-0.04512881860136986,
-0.6164644956588745,
-0.7279622554779053,
-0.7819955945014954,
-0.7906516194343567... |
javascript/reference/errors/getter_only/index.md | JavaScript - Errors - Getter only:
The JavaScript strict mode-only exception "setting getter-only property" occurs when there is an attempt to set a new value to a property for which only a getter is specified, or when setting a private accessor property that similarly only has a getter defined. | [
-0.6629041433334351,
-0.5226565599441528,
-1.785316824913025,
1.2559391260147095,
-0.4388650059700012,
-0.9457591772079468,
-0.018091514706611633,
1.4713934659957886,
-0.2988128960132599,
-0.28516528010368347,
-0.6937186121940613,
-1.1217479705810547,
-0.803128182888031,
-0.537301659584045... |
javascript/reference/errors/getter_only/index.md | JavaScript - Errors - Getter only - Message:
Example:
TypeError: Cannot set property x of #<Object> which has only a getter (V8-based)
TypeError: '#x' was defined without a setter (V8-based)
TypeError: setting getter-only property "x" (Firefox)
TypeError: Attempted to assign to readonly property. (Safari)
TypeError: ... | [
-1.4028421640396118,
-0.11697177588939667,
-1.686733365058899,
-0.03828682750463486,
-0.6763266921043396,
-0.748100221157074,
0.5731976628303528,
1.4220904111862183,
0.02757825329899788,
-0.62159663438797,
0.17682218551635742,
-0.7616358399391174,
-0.3709307312965393,
-1.096900463104248,
... |
javascript/reference/errors/getter_only/index.md | JavaScript - Errors - Getter only - Error type:
`TypeError` in strict mode only. | [
-0.8130961060523987,
-0.40899962186813354,
-1.434983491897583,
-0.03694668039679527,
-0.34929749369621277,
0.04039457440376282,
-0.03040468320250511,
2.0415232181549072,
-0.41757771372795105,
-0.3786945641040802,
-0.4840801954269409,
-1.1082762479782104,
-0.1927376389503479,
-0.21909883618... |
javascript/reference/errors/getter_only/index.md | JavaScript - Errors - Getter only - What went wrong?:
There is an attempt to set a new value to a property for which only a getter is specified. While this will be silently ignored in non-strict mode, it will throw a `TypeError` in strict mode. Classes are always in strict mode, so assigning to a getter-only private e... | [
-0.9863699674606323,
-0.4404878318309784,
-1.6238787174224854,
0.3169887661933899,
-0.14682438969612122,
-0.466104656457901,
-0.15559472143650055,
1.6323859691619873,
-0.16837649047374725,
-0.4842928349971771,
-0.19443058967590332,
-1.2848135232925415,
-0.4014049768447876,
-0.8171560764312... |
javascript/reference/errors/getter_only/index.md | JavaScript - Errors - Getter only - Examples - Property with no setter:
The example below shows how to set a getter for a property. It doesn't specify a setter, so a `TypeError` will be thrown upon trying to set the `temperature` property to `30`. For more details see also the `Object.defineProperty()` page.
Example:... | [
0.12548190355300903,
-0.8834290504455566,
-1.271450400352478,
1.3831405639648438,
0.43516403436660767,
-1.1151397228240967,
0.13323809206485748,
0.6653054356575012,
-0.13912585377693176,
-0.586292028427124,
0.2591076195240021,
-0.04191955178976059,
-0.6655852794647217,
0.03800293058156967,... |
javascript/reference/errors/called_on_incompatible_type/index.md | JavaScript - Errors - Called on incompatible type:
The JavaScript exception "called on incompatible target (or object)" occurs when a function (on a given object), is called with a `this` not corresponding to the type expected by the function. | [
0.5068675875663757,
-0.09287634491920471,
-0.9061334133148193,
0.8160462975502014,
0.09733960032463074,
-1.402524709701538,
0.5609853863716125,
0.19049641489982605,
-0.9310932755470276,
0.3281172811985016,
-0.3476454019546509,
-0.3834928572177887,
-0.06788218766450882,
-0.49423155188560486... |
javascript/reference/errors/called_on_incompatible_type/index.md | JavaScript - Errors - Called on incompatible type - Message:
Example:
TypeError: Method Set.prototype.add called on incompatible receiver undefined (V8-based)
TypeError: Bind must be called on a function (V8-based)
TypeError: Illegal invocation (V8-based)
TypeError: Function.prototype.toString requires that 'this' be... | [
-0.40241384506225586,
-0.3730631172657013,
-1.5167319774627686,
0.021848607808351517,
-0.03366556018590927,
-0.998662531375885,
0.08424285799264908,
0.3363456428050995,
-0.7394200563430786,
0.07016829401254654,
-0.3545028269290924,
-0.45007872581481934,
0.03949784114956856,
-0.455670535564... |
javascript/reference/errors/called_on_incompatible_type/index.md | JavaScript - Errors - Called on incompatible type - Error type:
`TypeError` | [
0.42861199378967285,
0.02462473139166832,
-1.1343439817428589,
-0.40500253438949585,
-0.13546723127365112,
0.29259350895881653,
0.9584597945213318,
1.4379284381866455,
-0.3297068178653717,
-0.4102814495563507,
0.24662740528583527,
-0.2957836985588074,
0.062191277742385864,
-0.5771885514259... |
javascript/reference/errors/called_on_incompatible_type/index.md | JavaScript - Errors - Called on incompatible type - What went wrong?:
When this error is thrown, a function (on a given object), is called with a `this` not corresponding to the type expected by the function.
This issue can arise when using the `Function.prototype.call()` or `Function.prototype.apply()` methods, and ... | [
-0.13146890699863434,
-0.0304192453622818,
-0.9498392939567566,
0.7625282406806946,
0.1670447140932083,
-0.5744193196296692,
-0.12732717394828796,
1.2229995727539062,
-0.41834044456481934,
-0.01987302117049694,
-0.295287549495697,
0.024884101003408432,
0.4869752824306488,
-0.04707270115613... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.