Exemple

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

Cas

Objectif

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

Paquets

@babel/preset-env 7.29.7

Environnement

node

Créé

2026-08-17T06:38:36Z

Ce que l'on suppose souvent

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

L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.

Contrat

• 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})');

Fichiers

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

Télécharger l’artefact source (tar.gz)

Seeder d'origine

csx-seed

Reçus de vérification

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