glsl-token-descope

v1.0.2

"Descope" an array of GLSL tokens such that they can be safely inlined alongside within another shader without causing any global variable conflicts. For more information about how to use this package see README

Latest version published 10 years ago

License: MIT

NPM

GitHub

Package Health Score

53 / 100

security
No known security issues
popularity
Popular
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
1.0.2	\|	03/2015	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (229,091)

GitHub Stars: 3
Forks: 2
Contributors: 1

Direct Usage Popularity

The npm package glsl-token-descope receives a total of 229,091 downloads a week. As such, we scored glsl-token-descope popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package glsl-token-descope, we found that it has been starred 3 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 1
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like glsl-token-descope is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 2
Open PR: 0
Last Release: 10 years ago
Last Commit: 10 years ago

Further analysis of the maintenance status of glsl-token-descope based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for glsl-token-descope is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 10 years
Dependencies: 4 Direct
Versions: 4
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 17
TS Typings: No

glsl-token-descope has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

glsl-token-descope

"Descope" an array of GLSL tokens such that they can be safely inlined alongside within another shader without causing any global variable conflicts.

Useful for modularising GLSL source files, e.g. as is done in glslify, but should be useful in other tools too.

Written with WebGL's GLSL syntax in mind – all the same, pull requests to support other variants would be much appreciated 😃

Usage

`descope(tokens, [rename(name)])`

Takes an array of GLSL tokens produced by glsl-tokenizer and renames variables to avoid global conflicts by modifying their "data" property in-place.

For example:

var tokenize  = require('glsl-tokenizer/string')
var descope   = require('glsl-token-descope')
var stringify = require('glsl-token-string')

var src = `
precision mediump float;

uniform mat4  top1;
uniform float top2;

void main() {
  float x = 1.0;
  gl_FragColor = vec4(vec3(x), top2);
}
`.trim()

var tokens = tokenize(src)

console.log(stringify(descope(tokens)))

Which should rename main, top1 and top2 to result in this output:

precision mediump float;

uniform mat4  top1_0;
uniform float top2_1;

void main_2() {
  float x = 1.0;
  gl_FragColor = vec4(vec3(x), top2_1);
}

Optionally, you may pass in a custom rename function as descope's second argument to choose how you rename your variables. For example, adding a custom rename function to the previous function:

descope(tokens, function(name) {
  return 'a_' + name
})

Would result in the following shader:

precision mediump float;

uniform mat4  a_top1;
uniform float a_top2;

void a_main() {
  float x = 1.0;
  gl_FragColor = vec4(vec3(x), a_top2);
}

License

MIT. See LICENSE.md for details.

glsl-token-descope dependencies

glsl-token-depth glsl-token-scope glsl-token-properties glsl-token-assignments

glsl-token-descope development dependencies

6to5 tape chalk tap-spec glsl-tokenizer glsl-token-string

FAQs

What is glsl-token-descope?

"Descope" an array of GLSL tokens such that they can be safely inlined alongside within another shader without causing ... Visit Snyk Advisor to see a full health score report for glsl-token-descope, including popularity, security, maintenance & community analysis.

Is glsl-token-descope popular?

The npm package glsl-token-descope receives a total of 229,091 weekly downloads. As such, glsl-token-descope popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is glsl-token-descope well maintained?

We found indications that glsl-token-descope is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is glsl-token-descope safe to use?

The npm package glsl-token-descope was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 18 December-2024, at 10:25 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

glsl-token-descope

"Descope" an array of GLSL tokens such that they can be safely inlined alongside within another shader without causing any global variable conflicts. For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (229,091)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Readme

glsl-token-descope

Usage

`descope(tokens, [rename(name)])`

See Also

License

glsl-token-descope dependencies

glsl-token-descope development dependencies

FAQs

What is glsl-token-descope?

Is glsl-token-descope popular?

Is glsl-token-descope well maintained?

Is glsl-token-descope safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (229,091)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

glsl-token-descope

Usage

descope(tokens, [rename(name)])

See Also

License

glsl-token-descope dependencies

glsl-token-descope development dependencies

FAQs

What is glsl-token-descope?

Is glsl-token-descope popular?

Is glsl-token-descope well maintained?

Is glsl-token-descope safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues

`descope(tokens, [rename(name)])`