Giter Site home page Giter Site logo

pratt-parser's Introduction

npm License bundlejs downloads GitHub Issues Build Status Styled with prettier Commitizen friendly Known Vulnerabilities Coverage Status

pratt-parser

Pratt Parser

Based on Top Down Operator Precedence and Douglas Crockford TDOP

import { Parser, WhiteSpaceToken, NumberToken } from "pratt-parser";

function Value(value) {
  return Object.create(null, {
    value: {
      value: value
    }
  });
}

const myGrammar = new Parser({
  tokens: [WhiteSpaceToken, NumberToken],
  prefix: {
    "(": {
      nud(grammar) {
        const e = grammar.expression(0);
        grammar.advance(")");
        return e;
      }
    }
  },
  infix: {
    ")": {},
    "+": {
      precedence: 50,
      combine: (left, right) => Value(left.value + right.value)
    },
    "-": {
      precedence: 50,
      combine: (left, right) => Value(left.value - right.value)
    },
    "*": {
      precedence: 60,
      combine: (left, right) => Value(left.value * right.value)
    },
    "/": {
      precedence: 60,
      combine: (left, right) => Value(left.value / right.value)
    }
  }
});

console.log(myGrammar.parse("(1 + (1 + 4 * 3)) * (2 + 1)").value);

API

Table of Contents

pratt-parser

pratt-parser

pratt-parser

RootToken

Base object for all tokens

parseString

Parses from chunk of PrasePosition and delivers next token Modifies ParsePosition so that it points behind the detected token.

Parameters

  • pp PrsePosition

Returns Token

WhiteSpaceToken

skip white space

LineCommentToken

skips until end of line

EOFToken

Token representing 'end of file'

Parser

Creates a grammar for later parsing

Parameters

  • grammar Object definition of the grammar with operators...
  • options

error

Forwards error to the tokenizer

Parameters

  • args ...any

Returns Object error

parse

Parses the input and delivers the outermoost expression.

Parameters

  • chunk string input text
  • context Object object transparently passed to tokenizer

Returns Object evaluated input

Tokenizer

Creates a tokenizer for later parsing.

Parameters

  • grammar Object definition of the grammar with operators...

tokens

delivers tokens from the input.

Parameters

  • chunk string the input to be processed
  • context Object additional info to be used by the actual token types

error

Parameters

Returns Object error

install

With npm do:

npm install pratt-parser

license

BSD-2-Clause

pratt-parser's People

Contributors

arlac77 avatar dependabot-preview[bot] avatar dependabot[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar snyk-bot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

zdenko rampall dyaso

pratt-parser's Issues

An in-range update of rollup is breaking the build 🚨

Version 0.45.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.45.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.45.1 at 95.868% Details
  • βœ… codecov/patch Coverage not affected when comparing efb88f0...f507e1d Details
  • βœ… codecov/project 95.86% remains the same compared to efb88f0 Details

Commits

The new version differs by 3 commits.

  • 87c4733 -> v0.45.1
  • 5e4cbdc Merge pull request #1489 from rollup/gh-1483
  • e099d8c remove weak from optionalDependencies

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.41.6 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.41.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ bitHound - Code 3 failing files. Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details

  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.41.6 at 93.258% Details

  • βœ… codecov/patch Coverage not affected when comparing 87bbf07...ab48364 Details

  • βœ… codecov/project 93.25% remains the same compared to 87bbf07 Details

Commits

The new version differs by 7 commits .

  • a96a923 -> v0.41.6
  • 7c8c6ba Merge pull request #1337 from krisselden/fix-cache-loader-sourcemaps
  • d94d8c2 Fix cache losing originalSourceMap for loaders with sourcemaps
  • ae9eb5c diction
  • d286702 Merge pull request #1330 from rollup/documentation
  • 5cafe1b license text
  • 5a718a2 quick start commands

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 11.2.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/nyc-11.2.0 at 97.727% Details
  • βœ… codecov/patch Coverage not affected when comparing b338acf...9b7c13d Details
  • βœ… codecov/project 97.72% (+1.85%) compared to b338acf Details

Commits

The new version differs by 7 commits.

  • b2ff72d chore(release): 11.2.0
  • 97b962e chore: explicit update of istanbul-lib-instrument (#662)
  • 0dcceda feat: allow cwd to be configured see #620
  • 0fc6d8f chore: add support for --cwd (#542) (#620)
  • 658dba4 fix: remove excluded files from coverage before writing (#649)
  • dd40dc5 feat: add possibility to filter coverage-maps (#637)
  • fb3ab92 docs: add link to community slack (#639)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.3.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - ❌ **bitHound - Code** 3 failing files. [Details](https://www.bithound.io/github/arlac77/pratt-parser/d7d1420c3778b431eb1ad811ec533e382b9be388/files#filter-failing-file),- βœ… **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/arlac77/pratt-parser/d7d1420c3778b431eb1ad811ec533e382b9be388/dependencies/npm?status=passing),- βœ… **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/arlac77/pratt-parser/builds/225180930),- βœ… **security/snyk** No new vulnerabilities [Details](https://snyk.io/test/github/arlac77/pratt-parser/d7d1420c3778b431eb1ad811ec533e382b9be388?fromStatus=true),- βœ… **continuous-integration/travis-ci/pr** The Travis CI build passed [Details](https://travis-ci.org/arlac77/pratt-parser/builds/225189038),- βœ… **coverage/coveralls** Coverage remained the same at 93.651% [Details](https://coveralls.io/builds/11211342),- βœ… **codecov/project** 93.65% remains the same compared to ff85588 [Details](https://codecov.io/gh/arlac77/pratt-parser/compare/ff8558878e9bdcfd4ed6d2c52ed346ca548febb0...d7d1420),- βœ… **codecov/patch** Coverage not affected when comparing ff85588...d7d1420 [Details](https://codecov.io/gh/arlac77/pratt-parser/compare/ff8558878e9bdcfd4ed6d2c52ed346ca548febb0...d7d1420)

Release Notes coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❀️

As highlights:

  • We've got coverage now!
  • Testing is looking less flaky \o/.
  • No more nitpicking about "mocha.js" build on PRs.

πŸŽ‰ Enhancements

  • #2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
  • #2769: Support --inspect-brk on command-line (@igwejk)

πŸ› Fixes

  • #2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

πŸ” Coverage

πŸ”© Other

Commits

The new version differs by 89 commits0.

  • fb1687e :ship: Release v3.3.0
  • 1943e02 Add Changelog for v3.3.0
  • 861e968 Refactor literal play-icon hex code to a var
  • 1d3c5bc Fix typo in karma.conf.js
  • 9bd9389 Fix spec paths in test HTML files
  • 0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)
  • 73929ad Comment special treatment of '+' in URL query parsing
  • e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts
  • 038c636 Support --inspect-brk on command-line
  • b4ebabd Merge pull request #2727 from lamby/reproducible-build
  • 882347b Please make the build reproducible.
  • a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
  • ed61cd0 cover .some() function in utils.js with tests
  • f42cbf4 Merge pull request #2701 from craigtaub/landingSpec
  • 6065242 use stubbed symbol

There are 89 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.51.3 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.51.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.51.3 at 95.763% Details
  • βœ… codecov/patch Coverage not affected when comparing 6989385...43442a2 Details
  • βœ… codecov/project 95.76% remains the same compared to 6989385 Details

Commits

The new version differs by 7 commits.

  • 6d0e492 0.51.3
  • 8680b29 Update changelog
  • 9d18aeb Merge pull request #1717 from rollup/fix-sequence-expressions
  • b5081ba * Forgot to forward the arguments for .render(code, es)
  • 3224778 Resolve #1707, resolve #1709
  • d04644a Merge remote-tracking branch 'nathancahill/broken-test-sequences' into fix-sequence-expressions
  • f79f508 add case for sequences with imports

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.41.5 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.41.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ bitHound - Code 3 failing files. Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details

  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.41.5 at 92.975% Details

  • βœ… codecov/project 93.25% remains the same compared to 3c5d629 Details

  • βœ… codecov/patch Coverage not affected when comparing 3c5d629...b566bf5 Details

Commits

The new version differs by 29 commits .

There are 29 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.37.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.37.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • βœ… continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

  • βœ… continuous-integration/gitbook/pdf GitBook build "pdf" succeeded Details

  • βœ… continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • ❌ bitHound - Code 2 failing files. Details

Commits

The new version differs by 21 commits .

  • b3b1098 -> v0.37.1
  • a804033 Merge pull request #450 from rollup/gh-447
  • 490d428 skip symlink test on windows
  • 70261d0 linting
  • 2d7f8a7 merge master -> gh-447
  • 3f39de8 Merge pull request #1143 from danez/recursive-functions
  • 583b13d Improves tree-shaking by only considering program-level
  • b04e790 Merge pull request #1152 from kzc/1146
  • dfb8a3f Merge pull request #1144 from christopherthielen/master
  • b1e4384 Update comments describing property string generation
  • 2521f2e be more leniant in processing ExportDefaultDeclaration (#1146)
  • bb546d3 Add test for bizzare moduleName
  • f43fd99 Access global.* using array notation
  • 98abe24 Merge pull request #1151 from rollup/gh-957
  • 2d32cdd implement gatherPossibleValues on ExternalDeclaration - fixes #957

There are 21 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 11.0.3 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.0.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 3 failing files. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/nyc-11.0.3 at 93.651% Details
  • βœ… codecov/patch Coverage not affected when comparing a3a51e0...2bac662 Details
  • βœ… codecov/project 93.65% remains the same compared to a3a51e0 Details

Commits

The new version differs by 4 commits.

  • e9fad9f docs: add note about tap-nyc to README (#614)
  • f86b0b1 chore(release): 11.0.3
  • 923b062 fix: upgrade to spawn-wrap version that works with babel-register (#617)
  • b1eb4d6 fix: update help link to list of reporters (#601)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.41.4 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.41.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • ❌ bitHound - Code 4 failing files. Details

  • βœ… continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

  • βœ… continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details

  • βœ… continuous-integration/gitbook/pdf GitBook build "pdf" succeeded Details

Commits

The new version differs by 5 commits .

  • 80da8ec -> v0.41.4
  • 23d50f6 Merge pull request #1262 from rollup/gh-1257
  • 5c88259 handle call expressions of uncallable things more gracefully (#1257)
  • 9c58833 Merge pull request #1261 from rollup/gh-1252
  • 457be9c handle multiple export * from external declarations (#1252)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of travis-deploy-once is breaking the build 🚨

Version 4.3.3 of travis-deploy-once was just published.

Branch Build failing 🚨
Dependency travis-deploy-once
Current Version 4.3.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

travis-deploy-once 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
  • ❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details

Release Notes v4.3.3

4.3.3 (2018-01-23)

Bug Fixes

  • package: update yargs to version 11.0.0 (cf1c97c)
Commits

The new version differs by 1 commits.

  • cf1c97c fix(package): update yargs to version 11.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.3.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.2.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - ❌ **bitHound - Code** 3 failing files. [Details](https://www.bithound.io/github/arlac77/pratt-parser/bc477885a41dc407da3c37027d34afe0474dfc75/files#filter-failing-file),- βœ… **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/arlac77/pratt-parser/bc477885a41dc407da3c37027d34afe0474dfc75/dependencies/npm?status=passing),- βœ… **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/arlac77/pratt-parser/builds/227086848?utm_source=github_status&utm_medium=notification),- βœ… **coverage/coveralls** First build on greenkeeper/nyc-10.3.0 at 93.651% [Details](https://coveralls.io/builds/11301536),- βœ… **codecov/patch** Coverage not affected when comparing bbef833...bc47788 [Details](https://codecov.io/gh/arlac77/pratt-parser/commit/bc477885a41dc407da3c37027d34afe0474dfc75),- βœ… **codecov/project** 93.65% remains the same compared to bbef833 [Details](https://codecov.io/gh/arlac77/pratt-parser/commit/bc477885a41dc407da3c37027d34afe0474dfc75)

Commits

The new version differs by 4 commits ahead by 4, behind by 2.

  • 55e826d chore(release): 10.3.0
  • 89dc7a6 chore: explicit update of istanbul dependnecies (#562)
  • 1887d1c feat: add support for --no-clean, to disable deleting raw coverage output (#558)
  • ff73b18 fix: source-maps were not being cached in the parent process when --all was being used (#556)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.51.8 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.51.7
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… security/snyk No new issues Details
  • βœ… continuous-integration/travis-ci/pr The Travis CI build passed Details
  • βœ… coverage/coveralls Coverage remained the same at 93.162% Details
  • βœ… codecov/project 93.16% remains the same compared to dcec023 Details
  • βœ… codecov/patch Coverage not affected when comparing dcec023...2bddd23 Details

Commits

The new version differs by 8 commits.

  • ab8d67f 0.51.8
  • e7fbec6 Update changelog
  • d6e95ce Merge pull request #1742 from rollup/update-dependencies
  • ba85f9c Update dependencies
  • 1042217 Merge pull request #1740 from rollup/refactor-assignment-handling
  • 945bb9d Fix typo
  • 5c37051 * Raise maximum path depth again
  • 690510f Simplify assignment -> reassignment tracking

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.41.2 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.41.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • βœ… continuous-integration/gitbook/pdf GitBook build "pdf" succeeded Details

  • βœ… continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

  • βœ… continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • ❌ bitHound - Code 4 failing files. Details

Commits

The new version differs by 9 commits .

  • e2d9b6b -> v0.41.2
  • 2a01a99 Merge pull request #1241 from kzc/0_41_0_changelog_addition
  • c038cda Merge pull request #1240 from rollup/gh-841-updated
  • 61528b7 change log addition for 0.41.0
  • 82b284d optimize ns["foo"] (#841)
  • 40a0ed5 Merge pull request #1239 from rollup/gh-1213
  • bc0f791 suppress warnings with --silent (closes #1213)
  • 6384b6c Merge pull request #1238 from rollup/gh-797
  • 101ad28 use options.indent for UMD block - fixes #797

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.45.2 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.45.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.45.2 at 95.868% Details
  • βœ… codecov/patch Coverage not affected when comparing 6f62825...d980bab Details
  • βœ… codecov/project 95.86% remains the same compared to 6f62825 Details

Commits

The new version differs by 12 commits.

  • b7a4edf -> v0.45.2
  • 66a6e88 Merge branch 'master' of github.com:rollup/rollup
  • e1e0f5a Merge pull request #1487 from TheWeatherCompany/twc-master
  • 2ff79f9 Merge pull request #1482 from Andarist/fix/cli-extend
  • 3e38651 Merge pull request #1490 from rollup/rollup-watch-gh-54
  • 3b2363f install rollup-watch as devDependency
  • e9ea331 separate resolvedIds from resolvedExternalIds
  • 782967a update LICENSE
  • b00bc3c Undo package.json changes
  • 2607d4e Change to use hasOwnProperty check vs in to prevent TypeError
  • 1bc1ea4 Change package name to @twc/rollup
  • be94551 Fixed --extend flag not being passed correctly from the CLI arguments

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.39.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.39.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • ❌ bitHound - Code 2 failing files. Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • βœ… continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

  • βœ… continuous-integration/gitbook/pdf GitBook build "pdf" succeeded Details

  • βœ… continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details

Commits

The new version differs by 8 commits .

  • 415985b -> v0.39.1
  • 38bb9d9 Merge pull request #1204 from rollup/gh-1198
  • d1d667f ignore var inits in dead branches - fixes #1198
  • 11a2830 Merge pull request #1202 from rollup/gh-1082
  • 532dff1 change recommendation to local installation of rollup-watch (#1082)
  • c597b91 Merge pull request #1200 from rollup/gh-1197
  • 708fb98 warn on missing format (fixes #1197)
  • 979cfc2 update a few dependencies

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of mocha-lcov-reporter is breaking the build 🚨

Version 1.3.0 of mocha-lcov-reporter just got published.

Branch Build failing 🚨
Dependency mocha-lcov-reporter
Current Version 1.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha-lcov-reporter is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/gitbook/pdf GitBook build "pdf" is pending Details

  • ❌ continuous-integration/gitbook/epub GitBook build "epub" is pending Details

  • ❌ continuous-integration/gitbook/mobi GitBook build "mobi" is pending Details

  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • ❌ bitHound - Code 3 failing files. Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 4 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.51.4 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.51.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.51.4 at 95.763% Details
  • βœ… codecov/project 95.76% remains the same compared to de41617 Details
  • βœ… codecov/patch Coverage not affected when comparing de41617...2bec3a5 Details

Commits

The new version differs by 6 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 11.1.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.0.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/nyc-11.1.0 at 95.868% Details
  • βœ… security/snyk No new vulnerabilities Details
  • ❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details
  • βœ… codecov/patch Coverage not affected when comparing 7ab87e8...f982fcf Details
  • βœ… codecov/project 95.86% remains the same compared to 7ab87e8 Details

Commits

The new version differs by 5 commits.

  • a3f033f chore(release): 11.1.0
  • a076951 chore: upgrade to latest version of istanbul-lib-instrument
  • 8768afe feat: upgrade to version of spawn-wrap that supports .EXE (#626)
  • 2d92501 chore: attempt to fix appveyor (#623)
  • bbadc1f feat: add support for per file coverage checking (#591)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.46.2 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.46.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… security/snyk No new vulnerabilities Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… continuous-integration/travis-ci/pr The Travis CI build passed Details
  • βœ… coverage/coveralls Coverage remained the same at 95.868% Details
  • βœ… codecov/project 95.86% remains the same compared to 44c96f7 Details
  • βœ… codecov/patch Coverage not affected when comparing 44c96f7...2b2ad79 Details

Commits

The new version differs by 7 commits.

  • 8e7cbe0 -> v0.46.2
  • 4451ee2 Merge pull request #1537 from rollup/gh-1480
  • 7a2a8d2 init rhs of for-in loop head with correct scope - fixes #1480
  • d0392e9 Merge pull request #1536 from rollup/gh-1533
  • a30f5a5 pass through all necessary options to bundle.write in rollup.watch (fixes #1533)
  • 834acb3 get test to pass
  • bd39fa3 allow passing interop through cli - true/false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.1.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/gitbook/json GitBook build "json" is pending Details

  • ❌ continuous-integration/gitbook/mobi GitBook build "mobi" is pending Details

  • ❌ continuous-integration/gitbook/website GitBook build "website" is pending Details

  • ❌ continuous-integration/gitbook/pdf GitBook build "pdf" is pending Details

  • ❌ continuous-integration/gitbook/epub GitBook build "epub" is pending Details

  • ❌ bitHound - Code 3 failing files. Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 14 commits .

  • 8f7af3a chore(release): 10.1.0
  • 8c58d68 fix: address edge-cases related to --all when instrumentation is disabled (#482)
  • 8b58c05 feat: allow eager instantiation of instrumenter (#490)
  • d8d2de0 feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
  • 7708235 chore: add test and docs for high and low watermarks (#493)
  • 0a1d72a feat: reporting watermarks can now be set in nyc config stanza (#469)
  • 1022b16 fix: pass configuration options to --check-coverage (#483)
  • 7b4c090 chore(package): update tap to version 9.0.3 (#488)
  • 093963b chore(release): 10.0.2
  • e01ec8c fix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)
  • 2e39e00 chore(release): 10.0.1
  • e0ef1d5 fix: upgrade spawn-wrap and istanbul-lib-instrument (#477)
  • 8603aa9 chore(package): update is-windows to version 1.0.0 (#466)
  • 64ae4f3 chore(package): update standard-version to version 4.0.0 (#461)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.2.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.1.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ bitHound - Code 3 failing files. Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details

  • βœ… coverage/coveralls First build on greenkeeper/nyc-10.2.0 at 93.258% Details

  • βœ… codecov/patch Coverage not affected when comparing 19b3fa7...0dabee1 Details

  • βœ… codecov/project 93.25% remains the same compared to 19b3fa7 Details

Commits

The new version differs by 6 commits .

  • 455619f chore(release): 10.2.0
  • 95cc09a feat: upgrade to version of yargs with extend support (#541)
  • 43535f9 chore: explicit update of istanbuljs dependencies (#535)
  • 98ebdff feat: allow babel cache to be enabled (#517)
  • 50adde4 feat: exclude the coverage/ folder by default πŸš€ (#502)
  • 6a59834 chore(package): update tap to version 10.0.0 (#507)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 8.0.1 of semantic-release just got published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 8.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As semantic-release is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/semantic-release-8.0.1 at 95.868% Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… codecov/patch Coverage not affected when comparing 638b431...616553d Details
  • βœ… codecov/project 95.86% remains the same compared to 638b431 Details

Release Notes v8.0.1

8.0.1 (2017-09-18)

Bug Fixes

Commits

The new version differs by 4 commits.

  • 8c44c31 fix(package): update @semantic-release/commit-analyzer to version 3.0.1
  • dd60b46 fix(package): update @semantic-release/release-notes-generator to version 4.0.0
  • 88b5895 docs(README): update commit lint suggestion (#429)
  • 1ceae83 docs(troubleshooting): initial version (#399)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.50.1 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.50.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.50.1 at 95.726% Details
  • βœ… codecov/patch Coverage not affected when comparing b8c7fc3...834f289 Details
  • βœ… codecov/project 95.72% remains the same compared to b8c7fc3 Details

Commits

The new version differs by 10 commits.

  • e773b58 0.50.1
  • ed2c00e Merge pull request #1660 from mjprude/hotfix/readme-starter-update
  • 8365bb1 Merge pull request #1695 from lukastaegert/do-not-exclude-pure-external-modules
  • c406f97 Resolve #1645
  • 63d9ef6 Merge pull request #1670 from Andarist/enhancement/as-git-dep
  • 59d801d Tweaked install/publish related scripts - enabled installing as dep directly from git
  • 5e16429 Merge pull request #1650 from corneliusweig/treeshake-sequence-expression
  • e5eb0ea Add SequenceExpression AST node resolving #1649
  • 7dd1baf Point Readme to up-to-date starter projects
  • ce0ceb8 Remove conditional expressions if they have no effect.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 11.2.1 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/nyc-11.2.1 at 95.868% Details
  • ❌ codecov/project 95.86% (-1.86%) compared to cdd143e Details
  • βœ… codecov/patch Coverage not affected when comparing cdd143e...2e186f5 Details

Commits

The new version differs by 3 commits.

  • 87281f9 chore(release): 11.2.1
  • 3bd1527 fix: create temp directory when --no-clean flag is set #663 (#664)
  • a10d478 fix: apply exclude logic before remapping coverage (#667)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.40.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.40.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • ❌ bitHound - Code 2 failing files. Details

  • βœ… continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

  • ❌ continuous-integration/gitbook/mobi GitBook build "mobi" failed Details

  • βœ… continuous-integration/gitbook/pdf GitBook build "pdf" succeeded Details

Commits

The new version differs by 3 commits .

  • 6cf998a -> v0.40.1
  • 7af9387 Merge pull request #1218 from rollup/export-default-no-space
  • e7fa75c handle export default{}

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 7.0.2 of semantic-release just got published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 7.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As semantic-release is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… security/snyk No new vulnerabilities Details
  • βœ… continuous-integration/travis-ci/pr The Travis CI build passed Details
  • βœ… coverage/coveralls Coverage remained the same at 95.868% Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… codecov/patch Coverage not affected when comparing bbaa806...752579d Details
  • βœ… codecov/project 95.86% remains the same compared to bbaa806 Details

Release Notes v7.0.2

7.0.2 (2017-08-16)

Bug Fixes

  • post: create v1.2.3 tag tag instead of branch (3f85597)

    Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY error :( To recover, follow these steps:

    1. Make sure you are on your main branch and pulled the latest changes from remote
    2. Edit the package.json file, set "version" to what ever should have been released. As an example, let's say the new version number would be 1.2.3. Save the change
    3. run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
    4. revert the changes
    5. create a tag with git tag v1.2.3 (put in the same version as in step 2. Push the tag to GitHub with git push --tags
    6. Manually create a release for the tag

    This will fix the problem and everything will work automagically again from here on now.

Commits

The new version differs by 1 commits.

  • 0c79a9b fix(post): create git tag properly

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 15.1.6 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.1.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v15.1.6

15.1.6 (2018-04-11)

Bug Fixes

  • match tag to tagFormat from the begining of the string (31ad231)
Commits

The new version differs by 2 commits.

  • 31ad231 fix: match tag to tagFormat from the begining of the string
  • a8a07b7 docs: clarify FAQ to publish non-JavaScript packages

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Feedback on markdown-doctest

Hello!

I see that you're using markdown-doctest! Great 😺

I was just reaching out to ask if you have any feedback around how it was to set up/use markdown-doctest.

Did you run into any pain points? Was anything particularly awesome?

(Please feel free to just close this issue if you don't have time to respond.)

An in-range update of mocha is breaking the build 🚨

Version 3.4.2 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.4.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 3 failing files. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… security/snyk No new vulnerabilities Details
  • βœ… continuous-integration/travis-ci/pr The Travis CI build passed Details
  • βœ… coverage/coveralls Coverage remained the same at 93.651% Details
  • βœ… codecov/project 93.65% remains the same compared to 809cbdd Details
  • βœ… codecov/patch Coverage not affected when comparing 809cbdd...1d40c6d Details

Release Notes fake-success

3.4.2 / 2017-05-24

πŸ› Fixes

πŸ”© Other

Commits

The new version differs by 7 commits.

  • a15b20a :ship: Release v3.4.2
  • fc802a9 :memo: Add Changelog for v3.4.2
  • 10ff0ec Eagerly set process.exitCode (#2820)
  • fc35691 Merge pull request #2818 from makepanic/issue/2802
  • 3e7152f Remove call to deprecated os.tmpDir (#2802)
  • e249434 Merge pull request #2807 from mochajs/npm-script-lint
  • 17a1770 Move linting into an npm script. Relates to #2805

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.52.1 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.52.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.52.1 at 93.162% Details

Commits

The new version differs by 14 commits.

  • d0ba36b Also lint bin folder
  • d74be7a 0.52.1
  • b19762d Update changelog
  • a44f75b Merge pull request #1774 from LostKobrakai/master
  • eadf109 Merge pull request #1768 from tivac/cli-multiple-envs
  • e63b11e Merge pull request #1759 from haraldrudell/master
  • d92f072 Merge pull request #1747 from adrianheine/master
  • 6e6fcc2 Let process.stdin actually trigger it’s end event
  • fe4bb17 feat: let --environment be specified multiple times
  • bcfa1bb Update changelog
  • 675aabb Merge pull request #1765 from rollup/improve-some-error-messages
  • 030eef7 * Improve deprecation warnings for some options
  • ab232a3 Use globals map for export name
  • 7976290 Support ES.Next object rest spread in config files like rollup.config.js

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of jsdoc-to-markdown is breaking the build 🚨

Version 3.0.2 of jsdoc-to-markdown was just published.

Branch Build failing 🚨
Dependency jsdoc-to-markdown
Current Version 3.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

jsdoc-to-markdown 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.

Status Details
  • ❌ bitHound - Dependencies null Details
  • ❌ bitHound - Code null Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/jsdoc-to-markdown-3.0.2 at 93.162% Details
  • βœ… security/snyk No new issues Details
  • ❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details
  • βœ… codecov/project 93.16% remains the same compared to b8b0a47 Details
  • βœ… codecov/patch Coverage not affected when comparing b8b0a47...a647480 Details

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.43.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.43.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.43.1 at 95.868% Details
  • βœ… codecov/patch Coverage not affected when comparing bd34448...df0c047 Details
  • βœ… codecov/project 95.86% remains the same compared to bd34448 Details

Commits

The new version differs by 28 commits.

There are 28 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.47.5 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.47.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.47.5 at 95.868% Details
  • βœ… codecov/project 95.86% remains the same compared to 5571b88 Details
  • βœ… codecov/patch Coverage not affected when comparing 5571b88...d18f72b Details

Commits

The new version differs by 3 commits.

  • 9cfada0 -> v0.47.5
  • 714ae2d Merge pull request #1558 from rollup/gh-1532
  • 8ec3e0d use Promise.resolve in mapSequence, to ensure each item is thenable - fixes #1532

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup-plugin-commonjs is breaking the build 🚨

Version 6.0.1 of rollup-plugin-commonjs just got published.

Branch Build failing 🚨
Dependency rollup-plugin-commonjs
Current Version 6.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup-plugin-commonjs is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/gitbook/pdf GitBook build "pdf" is pending Details

  • βœ… continuous-integration/gitbook/json GitBook build "json" succeeded Details

  • βœ… continuous-integration/gitbook/website GitBook build "website" succeeded Details

  • βœ… bitHound - Dependencies No failing dependencies. Details

  • ❌ bitHound - Code 2 failing files. Details

  • βœ… continuous-integration/gitbook/epub GitBook build "epub" succeeded Details

  • βœ… continuous-integration/gitbook/mobi GitBook build "mobi" succeeded Details

Commits

The new version differs by 3 commits .

  • 16c4a9c -> v6.0.1
  • d8274cf Merge pull request #152 from rollup/gh-127
  • 3acc5d6 dont overwrite globals (#127)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.60.1 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.60.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 7 commits.

  • 264c867 0.60.1
  • d1b13f2 Merge branch 'large-var-count'
  • 647460f Merge branch 'ongenerate-fix'
  • fbde57e fix input validation after options hook
  • b0eda7c include fix for chunkId closure
  • 2b0b6c9 fix ongenerate signature regression
  • 662ee81 fix large variable count numbering

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.3.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 3 failing files. Details,- βœ… bitHound - Dependencies No failing dependencies. Details,- βœ… continuous-integration/travis-ci/push The Travis CI build passed Details,- βœ… security/snyk No new vulnerabilities Details,- βœ… continuous-integration/travis-ci/pr The Travis CI build passed Details,- βœ… coverage/coveralls Coverage remained the same at 93.651% Details,- βœ… codecov/patch Coverage not affected when comparing d975fad...4c01236 Details,- βœ… codecov/project 93.65% remains the same compared to d975fad Details

Release Notes v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

  • allowUncaught added to commandline as --allow-uncaught (and bugfixed)
  • warning-related Node flags

πŸŽ‰ Enhancements

πŸ› Fixes

πŸ”© Other

Commits

The new version differs by 9 commits0.

  • 7554b31 Add Changelog for v3.4.0
  • 9f7f7ed Add --trace-warnings flag
  • 92561c8 Add --no-warnings flag
  • ceee976 lint test/integration/fixtures/simple-reporter.js
  • dcfc094 Revert "use semistandard directly"
  • 93392dd no special case for macOS running Karma locally
  • 4d1d91d --allow-uncaught cli option
  • fb1e083 fix allowUncaught in browser
  • 4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Tokenize real numbers to

Currenly online positive Naturalist can be parsed.
Externe the tokenizer to support real number (also the sientific notation)

An in-range update of rollup is breaking the build 🚨

Version 0.47.3 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.47.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.47.3 at 95.868% Details
  • βœ… codecov/project 95.86% remains the same compared to 217bb07 Details
  • βœ… codecov/patch Coverage not affected when comparing 217bb07...a64d95d Details
  • βœ… security/snyk No new vulnerabilities Details
  • ❌ continuous-integration/travis-ci/pr The Travis CI build is in progress Details

Commits

The new version differs by 7 commits.

  • 6b94155 -> v0.47.3
  • 586e255 Merge pull request #1551 from rollup/gh-1550
  • c364ec4 deshadow aliased imports (#1550)
  • 1b48335 Merge pull request #1549 from alippai/patch-1
  • a1c19b8 Add appveyor NodeJS 8 builds
  • ae996b7 Add travis for NodeJS 8
  • 3353338 check for process.hrtime, closes #1495

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.47.2 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.47.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.47.2 at 95.868% Details
  • βœ… codecov/patch Coverage not affected when comparing f45f418...dcd5703 Details
  • βœ… codecov/project 95.86% remains the same compared to f45f418 Details

Commits

The new version differs by 1 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.3.2 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.3.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details,- βœ… security/snyk No new vulnerabilities Details,- ❌ bitHound - Code 3 failing files. Details,- βœ… bitHound - Dependencies No failing dependencies. Details,- βœ… continuous-integration/travis-ci/pr The Travis CI build passed Details,- βœ… coverage/coveralls Coverage remained the same at 93.651% Details,- βœ… codecov/project 93.65% remains the same compared to 62fa0b8 Details,- βœ… codecov/patch Coverage not affected when comparing 62fa0b8...233be2b Details

Commits

The new version differs by 2 commits0.

  • e062a86 chore(release): 10.3.2
  • 213206f fix: we should not create a cache folder if cache is false (#567)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.46.3 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.46.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.46.3 at 95.868% Details
  • βœ… codecov/patch Coverage not affected when comparing ef3fba8...50ac150 Details
  • βœ… codecov/project 95.86% remains the same compared to ef3fba8 Details

Commits

The new version differs by 13 commits.

  • b7e1d49 -> v0.46.3
  • 55b2e46 install console-group for debugging convenience
  • c6af5c9 Merge pull request #1542 from rollup/gh-1538
  • f8f2fa7 init for loop scopes correctly
  • 5dec01d Merge pull request #1541 from rollup/gh-1488
  • 0e5f8b6 deshadow indirectly-imported namespaces (#1488)
  • 2e76960 Merge branch 'master' of github.com:rollup/rollup
  • e70dad3 Merge pull request #1540 from rollup/gh-1511
  • a44f442 lint
  • 483dc69 use source-map-support in development
  • cc0e5c7 dont include empty imports for reexported external modules
  • 671757e treat reexports differently from exports
  • 6ba6440 fix external namespace imports in es output (#1511)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.46.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.46.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.46.1 at 95.868% Details
  • βœ… codecov/project 95.86% remains the same compared to 4a075a8 Details
  • βœ… codecov/patch Coverage not affected when comparing 4a075a8...28846f6 Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 19 commits.

  • 8969272 -> v0.46.1
  • 0d5669b Merge pull request #1529 from rollup/gh-1528
  • f9f389c Merge pull request #1531 from rollup/gh-1530
  • 5d651a7 only ship .js files
  • b962cf6 separate node entry from browser entry
  • d8d5eec update config
  • e8da9f5 remove source-map-support
  • aa2b54b Merge pull request #1527 from rollup/tidy-up-tests
  • 0015e05 about to lose my sense of humour
  • 7cd8717 GODDAMMIT
  • 75152bf almost there
  • b38632e AARGGHHHH
  • 2c05caa please let this work
  • b9d0779 losing my goddamn mind over here
  • 6eba4d1 wtf. why are these tests passing locally but not in ci

There are 19 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.51.6 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.51.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.51.6 at 93.162% Details
  • βœ… codecov/patch Coverage not affected when comparing cdf02aa...519c856 Details
  • βœ… codecov/project 93.16% remains the same compared to cdf02aa Details

Commits

The new version differs by 5 commits.

  • 2e09e21 0.51.6
  • 5781ee5 Update changelog
  • d9558ae Merge pull request #1728 from misoguy/master
  • bb7411a Add getOriginalLocation method into Module.js to return correct error location
  • 4ad48c3 Add test to verify error object after transform not showing correct location

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.51.2 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.51.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.51.2 at 95.763% Details
  • βœ… codecov/patch Coverage not affected when comparing 8695cb3...76f3bd4 Details
  • βœ… codecov/project 95.76% remains the same compared to 8695cb3 Details

Commits

The new version differs by 4 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of chai is breaking the build 🚨

Version 4.0.1 of chai just got published.

Branch Build failing 🚨
Dependency chai
Current Version 4.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As chai is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 3 failing files. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/chai-4.0.1 at 93.651% Details
  • βœ… codecov/project 93.65% remains the same compared to 401aaa8 Details
  • βœ… codecov/patch Coverage not affected when comparing 401aaa8...2829b54 Details

Release Notes 4.0.1 / 2017-05-31

4.0.1

Of course, any major release cannot go without a quick bugfix release shortly after - and here's ours!

Bug Fixes

  • Remove package.json browser field which was mistakenly added, and caused bundler tools like Browserify or Webpack to fail as it attempted to rebundle an already bundled file. (#978, #982)
Commits

The new version differs by 2 commits.

  • b38b8d7 fix: (#978) remove browser field (#982)
  • d0ace69 Update supported node version badge in README FIX #975

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.51.7 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.51.6
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

rollup 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.

Status Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.51.7 at 93.162% Details
  • βœ… codecov/project 93.16% remains the same compared to 4e1932a Details
  • βœ… codecov/patch Coverage not affected when comparing 4e1932a...6128705 Details

Commits

The new version differs by 6 commits.

  • 172d72a Fix code style
  • 923b6fd 0.51.7
  • 03c6b90 Update changelog
  • 1d05530 Merge pull request #1724 from nathancahill/fix-sequence-this-context
  • a9b842c add function test for sequence context
  • 6b1c0bc maintain this context when sequence is callable

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.