KhronosGroup / KhronosGroup/WebGLDeveloperTools

Version Tag needed by Module Registries

Offen
#2 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
JavaScript
Sterne
222
Forks
75
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

TL;DR: God I hate to ask for yet-another favor. But .. could we place a sem-ver version on webgl-debug?

Details:
The maintainers of the JSPM registry like to have version tags so that they can deal with varying version within a complex set of dependencies. They may be able to use the commit SHA but would much prefer a version tag. Even tho webgl-debug hasn't changed in almost 4 years!

The good news is, if you can do this, webgl-debug will have a lovely registry that uses HTTP2/SPDY for mind-blowing micro-module speeds.

Micro modules are becoming popular in webgl via the stack.gl suite of modules. They even got toji's superb matrix library and refactored into seriously tiny modules. I haven't tried it yet but looks like a good idea. I wish shaders supported modules, but "glsl-ify" is the next best thing.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start by reviewing the repository's existing release tags and the webgl-debug history to determine the intended semver version. Add a semver version tag for webgl-debug and verify that the tag is suitable for JSPM and other module registries.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript
Bereich
release
Issue-Typ
Feature
Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.