Ejemplo

prove that transpiling a named capture group regex mutates its serialization shape by stripping the named groups from its .source property, even though evaluation semantics are preserved

sha256:15dd17f193ef111f72ee349d6af1c3b8051e9157c5ba59126ce65b3d88afd6d1

Caso

Objetivo

prove that transpiling a named capture group regex mutates its serialization shape by stripping the named groups from its .source property, even though evaluation semantics are preserved HOW

Paquetes

@babel/preset-env 7.29.7

Entorno

node

Creado

2026-08-17T06:38:36Z

Lo que suele suponerse

a regular expression with named capture groups compiled by Babel will preserve the exact syntactic shape of the pattern in its .source property

El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.

Contrato

• the .source property of a named capture group regex transpiled for IE11 evaluates to a string stripped of the capture group names, rather than the original source string
• assert.strictEqual(nativeRegex.source, '(?<year>\\d{4})-(?<month>\\d{2})-(?<day>\\d{2})');
• assert.strictEqual(transpiledRegex.source, '(\\d{4})-(\\d{2})-(\\d{2})');

Archivos

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test.mjs
• test/contract.mjs

Descargar el artefacto de código fuente (tar.gz)

Seeder de origen

csx-seed

Recibos de verificación

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9