KhronosGroup / KhronosGroup/WebGLDeveloperTools

Version Tag needed by Module Registries

Open
#2 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
222
Forks
75
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
release
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.