[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1124441: ITP: node-is-potential-custom-element-name -- Checks if a string matches the HTML PotentialCustomElementName specification





Le jeu. 1 janv. 2026 à 13:47, Edward Betts <edward@4angle.com> a écrit :
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.

This is a package that hasn't seen any update for five years,
and it is distributes just a single regexp.

This package is an indirect dependency of the Home Assistant frontend.

Can you be more specific - what is the chain of dependencies ?

Home Assistant is a smart home platform. I plan to maintain this package as
part of the _javascript_ team.

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/

Jérémy

Happy New Year.

Reply to: