Installations

npm install regenerator-runtime

Score

100

Supply Chain

76.7

Quality

76.9

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

19

Total

448

Closed

230

Merged

199

Issues

Open

63

Total

269

Closed

206

Releases

37

runtime@0.10.5

Published on 28 Apr 2017

runtime@0.10.4

Published on 28 Apr 2017

v0.9.7

Published on 17 Feb 2017

v0.9.6

Published on 17 Feb 2017

v0.8.6

Published on 14 Jan 2015

v0.8.2

Published on 04 Jan 2015

View all 37 releases

Developer

facebook

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

20.7.0

NPM Version

10.1.0 Statistics

3,830 Stars

1,110 Commits

1,161 Forks

90 Watching

26 Branches

136 Contributors

Updated on 28 Nov 2024

Languages

JavaScript (99.46%)

Shell (0.32%)

HTML (0.23%)

Total Downloads

Cumulative downloads

Total Downloads

11,683,408,192

Last day

-7.8%

11,943,723

Compared to previous day

Last week

2%

70,155,244

Compared to previous week

Last month

13.2%

285,561,542

Compared to previous month

Last year

20.5%

2,949,947,280

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

regenerator

This package implements a fully-functional source transformation that takes the syntax for generators/yield from ECMAScript 2015 or ES2015 and Asynchronous Iteration proposal and spits out efficient JS-of-today (ES5) that behaves the same way.

A small runtime library (less than 1KB compressed) is required to provide the wrapGenerator function. You can install it either as a CommonJS module or as a standalone .js file, whichever you prefer.

Installation

From npm:

1npm install -g regenerator

From GitHub:

1cd path/to/node_modules
2git clone git://github.com/facebook/regenerator.git
3cd regenerator
4npm install .
5npm test

Usage

You have several options for using this module.

Simplest usage:

1regenerator es6.js > es5.js # Just the transform.
2regenerator --include-runtime es6.js > es5.js # Add the runtime too.
3regenerator src lib # Transform every .js file in src and output to lib.

Programmatic usage:

1var es5Source = require("regenerator").compile(es6Source).code;
2var es5SourceWithRuntime = require("regenerator").compile(es6Source, {
3  includeRuntime: true
4}).code;

AST transformation:

1var recast = require("recast");
2var ast = recast.parse(es6Source);
3ast = require("regenerator").transform(ast);
4var es5Source = recast.print(ast);

How can you get involved?

The easiest way to get involved is to look for buggy examples using the sandbox, and when you find something strange just click the "report a bug" link (the new issue form will be populated automatically with the problematic code).

Alternatively, you can fork the repository, create some failing tests cases in test/tests.es6.js, and send pull requests for me to fix.

If you're feeling especially brave, you are more than welcome to dive into the transformer code and fix the bug(s) yourself, but I must warn you that the code could really benefit from better implementation comments.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

9

Security-Policy

Determines if the project has published a security policy.

4

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

1

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

Score

4.1

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More