Is this an ES6 generator function?
License: MIT License
Is this a native generator function?
var isGeneratorFunction = require('is-generator-function');
assert(!isGeneratorFunction(function () {}));
assert(!isGeneratorFunction(null));
assert(isGeneratorFunction(function* () { yield 42; return Infinity; }));Simply clone the repo, npm install, and run npm test
| Branch | Build failing 🚨 |
|---|---|
| Dependency | uglify-js |
| Current Version | 3.3.2 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
uglify-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 10 commits.
8ca4915 v3.3.3b95e333 fix pure_getters on AST_Binary (#2681)e40a0ee improve assignment variations (#2671)cb62bd9 fix function inlining within loops (#2675)f30790b fix dead_code on return assignments (#2668)5205dbc retain recursive function names (#2667)3ff625d fix bugs on substituted AST_Defun (#2661)4832bc5 replace single-use recursive functions (#2659)7f342cb suppress inline within substituted AST_Scope (#2658)05e7d34 improve unused over duplicate variable names (#2656)See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
"Content Security Policy: The page’s settings blocked the loading of a resource at eval (“script-src”)."
No CSP warnings. Is there any other way to detect generator support?
When this code is run by next.js in Firefox, the warnings appears:
try {
return Function('return function*() {}')();
} catch (e) {
}Related issue: vercel/next.js#23587
| Branch | Build failing 🚨 |
|---|---|
| Dependency | eslint |
| Current Version | 4.14.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
ignoreComments option to indent rule (fixes #9018) (#9752) (Kevin Partington)The new version differs by 14 commits.
e14ceb0 4.15.02dfc3bd Build: changelog update for 4.15.06ab04b5 New: Add context.report({ messageId }) (fixes #6740) (#9165)fc7f404 Docs: add url to each of the rules (refs #6582) (#9788)fc44da9 Docs: fix sort-imports rule block language (#9805)65f0176 New: CLIEngine#getRules() (refs #6582) (#9782)c64195f Update: More detailed assert message for rule-tester (#9769)9fcfabf Fix: no-extra-parens false positive (fixes: #9755) (#9795)61e5fa0 Docs: Add table of contents to Node.js API docs (#9785)4c87f42 Fix: incorrect error messages of no-unused-vars (fixes #9774) (#9791)bbabf34 Update: add ignoreComments option to indent rule (fixes #9018) (#9752)db431cb Docs: HTTP -> HTTPS (fixes #9768) (#9768)cbf0fb9 Docs: describe how to feature-detect scopeManager/visitorKeys support (#9764)f7dcb70 Docs: Add note about "patch release pending" label to maintainer guide (#9763)See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Using the regexp solution is buggy and inefficient. An easier check is to just fn.constructor.name === 'GeneratorFunction'.
isGeneratorFunction({*g(){}}.g) reports false in V8.
Current toString output for generator methods in V8 (at v8/v8@7611aac):
d8> ({*g(){}}.g).toString()
"*g(){}"
d8> "use strict"; (class {*g(){}}.prototype.g).toString()
"*g(){}"
d8> "use strict"; (class {static *g(){}}.g).toString()
"*g(){}"
When i excute npm install [email protected] ；
I get this error: No matching version found for [email protected];
But this version is always shown on https://web-bnpm.byted.org/package/is-generator-function；
And excute npm view is-generator-function versions. I get [
'1.0.0', '1.0.1',
'1.0.2', '1.0.3',
'1.0.4', '1.0.5',
'1.0.6', '1.0.7',
'1.0.8'
]
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.
Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.
If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.
We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.
13.0.0 to 13.1.0.This version is covered by your current version range and after updating it in your project the build failed.
@ljharb/eslint-config is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 5 commits.
2dd67e5 v13.1.034a402a [Minor] update config and require eslint v5.11fd1f310 [Dev Deps] update eslint, replace, safe-publish-latest, semver2d1a944 [Tests] use npm audit instead of nspa02c14b [Tests] up to node v11.6, v10.15, v8.15, v6.16See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Been using this lib for awhile, no problems so far, but do you see anything wrong with the following implementation?
isGeneratorFn: function(fn){
const str = String(fn);
const indexOfFirstParen = str.indexOf('(');
const indexOfFirstStar = str.indexOf('*');
return indexOfFirstStar < indexOfFirstParen;
},not sure if it's faster, but probably less convoluted logic and possibly won't break if underlying stuff changes. You are calling toString on fn in your logic, just like I do, which seems like the most expensive thing in both our implementations. but I believe the above implementation is both simpler and more robust.
I tried to compare the performance of 3 ways checking generator function, here is the jsperf.com page
It seems the performance is Obejct#toString > Object.getPrototypeOf > Function#toString, so it is better to place Object#toString and Object.getPrototypeOf before the Function#toString check, it seems no compatibility issue to me.
If acceptable, I can create a pull request for this issue.
Do you have a fetiche for complexity or is there a reason I am missing about why is the Makefile so complex? Why not using npm scripts, a simple .sh script or a Brocoli salad?
Cheers! 😄
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.nvmrc with the new onepackage.json files, so that was left aloneIf you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.
engines was only updated if it defined a single version, not a range..nvmrc was updated to Node.js 10.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The npm package for this module currently contains a 712 kB testling output file:
https://unpkg.com/[email protected]/
Would it be possible to add it to .gitignore?
This file and some other files could be ignored in the npm package .
1.0.0 to 1.0.1.This version is covered by your current version range and after updating it in your project the build failed.
replace is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The generator is always transpiled to plain function so... it is impossible to know
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These branches will be created by Renovate only once you click their checkbox below.
eslint to v8.57.0eslint to v9nyc to v17.github/workflows/node-aught.yml
.github/workflows/node-harmony.yml
.github/workflows/node-pretest.yml
.github/workflows/node-tens.yml
.github/workflows/rebase.yml
.github/workflows/require-allow-edits.yml
package.json
has-tostringtag ^1.0.0@ljharb/eslint-config ^21.0.0aud ^2.0.1auto-changelog ^2.4.0core-js ^2.6.5 || ^3.20.0eslint =8.8.0in-publish ^2.0.1make-generator-function ^2.0.0npmignore ^0.3.0nyc ^10.3.2safe-publish-latest ^2.0.0tape ^5.6.1uglify-register ^1.0.1node >= 0.4
.nvmrc
| Branch | Build failing 🚨 |
|---|---|
| Dependency | eslint |
| Current Version | 4.10.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
lines-around-comment (#9589) (Clément Fiorio)npm test (#9590) (Teddy Katz)no-invalid-this. (#9542) (Francisc)The new version differs by 35 commits.
1a9a6a5 4.11.0ef4d268 Build: changelog update for 4.11.0d4557a6 Docs: disallow use of the comma operator using no-restricted-syntax (#9585)d602f9e Upgrade: espree v3.5.2 (#9611)4def876 Chore: avoid handling rules instances in config-validator (#9364)fe5ac7e Chore: fix incorrect comment in safe-emitter.js (#9605)6672fae Docs: Fixed a typo on lines-between-class-members doc (#9603)980ecd3 Chore: Update copyright and license info (#9599)cc2c7c9 Build: use Node 8 in appveyor (#9595)2542f04 Docs: Add missing options for lines-around-comment (#9589)b6a7490 Build: ensure fuzzer tests get run with npm test (#9590)1073bc5 Build: remove shelljs-nodecli (refs #9533) (#9588)7e3bf6a Fix: edge-cases of semi-style (#9560)e5a37ce Fix: object-curly-newline for flow code (#9458)9064b9c Chore: add equalTokens in ast-utils. (#9500)There are 35 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.6.0 to 2.6.1.This version is covered by your current version range and after updating it in your project the build failed.
core-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 3 commits.
a5def74 2.6.13866e96 Merge pull request #465 from nicolo-ribaudo/fix-regression-463af4a972 Fix bug #463See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
your code is cool!!! but it can not test pass under the code uglified
| Branch | Build failing 🚨 |
|---|---|
| Dependency | uglify-register |
| Current Version | 1.0.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
uglify-register is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 10 commits.
d5763d3 v1.0.127fcf48 [Dev Deps] update eslintd90a4bd [Fix] uglify v3.3 re-added .parsedccbe9f [Tests] restore uglify version testing, broken in f3dfc92035b7c6f4081a87a548f3e94c47bfa555bb9a4d5 [Dev Deps] update eslint, nspa1232a6 [Tests] on node v9; pin included builds to LTS.0d8cf90 [Dev Deps] downgrade nyc to v10, to retain old node compat.6ef382c [Dev Deps] update nsp, nyc, eslintf3dfc92 [Tests] on latest node minors; use nvm install-latest-npm to ensure newer npm doesn’t break older nodea9aab78 [Dev Deps] update eslint, @ljharb/eslint-config, nsp, nyc, tapeSee the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
3.4.6 to 3.4.7.This version is covered by your current version range and after updating it in your project the build failed.
core-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The build errored.There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.