zloirock/core-js

URL punycode differs from nodejs / chrome behaviour

Open

#1,223 opened on Mar 17, 2023

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (1,609 forks)batch import
bughelp wanted

Repository metrics

Stars
 (23,771 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Consider the following url which has non-ascii characters: https://𝚍𝚒𝚜𝚌𝚘𝚛𝚍.gg

While trying to parse this for the hostname, both nodejs and chrome return ascii string discord.gg but corejs returns xn--ci2hbbs5ase.gg

Here is the code:

import configurator from 'core-js-pure/configurator.js';

configurator({
    // By default polyfills are not used if they are available natively.
    usePolyfill: ['URL'], // Override that behaviour for URL.
});

import URL from 'core-js-pure/web/url.js'; // For URL

const url = new URL('https://𝚍𝚒𝚜𝚌𝚘𝚛𝚍.gg');
console.log(url.hostname);

Contributor guide

Research direction
Investigate core js URL punycode encoding logic and compare with Node.js/Chrome's behavior; trace the hostname parsing in URL constructor to identify where the conversion diverges.
Tech stack
javascript
Domain
api
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65