Bug#1124441: marked as done (ITP: node-is-potential-custom-element-name -- Checks if a string matches the HTML PotentialCustomElementName specification)
Your message dated Wed, 7 Jan 2026 14:41:48 +0000
with message-id <aV5vYhuJTq6OgV8t@4angle.com>
and subject line Re: Bug#1124441: ITP: node-is-potential-custom-element-name -- Checks if a string matches the HTML PotentialCustomElementName specification
has caused the Debian Bug report #1124441,
regarding ITP: node-is-potential-custom-element-name -- Checks if a string matches the HTML PotentialCustomElementName specification
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1124441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124441
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Edward Betts <edward@4angle.com>
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name : node-is-potential-custom-element-name
Version : 1.0.1
Upstream Author : Mathias Bynens (https://mathiasbynens.be/)
* URL : https://github.com/mathiasbynens/is-potential-custom-element-name
* License : Expat
Programming Lang: JavaScript
Description : Checks if a string matches the HTML PotentialCustomElementName specification
This library provides a function to determine whether a given string conforms
to the PotentialCustomElementName production as specified in the HTML
Standard. This validation is necessary for web components or elements that
require custom element names according to the HTML naming rules.
.
Node.js is an event-based server-side JavaScript engine.
This package is an indirect dependency of the Home Assistant frontend.
Home Assistant is a smart home platform. I plan to maintain this package as
part of the JavaScript team.
--- End Message ---
--- Begin Message ---
Jérémy Lal <kapouer@melix.org> wrote:
> Le jeu. 1 janv. 2026 à 13:47, Edward Betts <edward@4angle.com> a écrit :
> > This package is an indirect dependency of the Home Assistant frontend.
>
> Can you be more specific - what is the chain of dependencies ?
home-assistant-frontend
-> eslint-plugin-wc
-> is-valid-element-name
-> is-potential-custom-element-name
> When a package has dependencies that are somewhat old and useful only in
> some specific case,
> it might make more sense to bundle it (in a multiple upstream tarball, or
> even embedded in debian/, depending on the usage).
> Please refer to our wiki pages:
> https://wiki.debian.org/Javascript
> https://wiki.debian.org/Javascript/GroupSourcesTutorial
> and also the many examples you could find in
> https://sources.debian.org/
Thanks for your message. You're right, we don't need this package, I'll
bundle it with either is-valid-element-name or eslint-plugin-wc.
I'm closing this ITP.
Cheers,
Edward
Happy new Year!
--- End Message ---
Reply to: