Giter Site home page Giter Site logo

brolog's Introduction

Mr. Huan Li is a serial entrepreneur and active angel investor with a strong technology background. He is a widely recognized technical leader in conversational AI and open-source cloud architectures. Huan is a GitHub Star, top open-source contributor in both US(#4) and China(#7), co-authored guide books "Chatbot 0 to 1" and "Concise Handbook of TensorFlow 2" and has been recognized by Microsoft, Google, and Tencent as MVP, GDE, and TVP. He is a Chatbot Architect and regularly speaks at technical conferences worldwide. Please find out more about his experiences at https://www.linkedin.com/in/huan42/

Wechaty

TypeScript ES Modules NPM Version Downloads Docker Pulls GitHub stars Discord

Huan is the creator and core developer of Wechaty Wechaty GitHub Stars. Wechaty is a Conversational RPA SDK for chatbot makers. With only six lines of code, you can create a bot on the most popular IMs like WeChat, Whatsapp, WeCom, Gitter, QQ, etc.

Star History Chart

Some numbers for the Wechaty project:

Below are his contributions (PRs and Issues) to GitHub open-source projects:

  • ♏️ means he is the creator or maintainer of the project
  • ©️ means he has contributed to the project

Chatbot Ecosystem

Chatbot Projects

Machine Learning & Conversational AI

Community

RxJS & Event-driven Programming

OpenAPI

Docker & Networking

Remote Procedure Call (RPC)

Database

Frida & Assembly

TypeScript

Web & Apps

Library & Tools

brolog's People

Contributors

dependabot-preview[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar huan avatar npmcdn-to-unpkg-bot avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar

Forkers

npmcdn-to-unpkg-bot

brolog's Issues

An in-range update of source-map is breaking the build 🚨

Version 0.7.3 of source-map was just published.

Branch Build failing 🚨
Dependency source-map
Current Version 0.7.2
Type devDependency

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

source-map 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
Commits

The new version differs by 16 commits.

  • b2171d5 Bump to version 0.7.3
  • 86d2f30 Merge pull request #336 from hildjj/classes
  • 14de5f8 Address comments in code review
  • 1ea5ee3 First stab at classes. source-map-consumer is a mess in order to keep the API the same. That file needs careful review. Everything else is pretty straightforward. Fixes #334. Fixes #259.
  • adfd0fb Merge pull request #335 from hildjj/coverage
  • 39db032 Add code coverage instructions to CONTRIBUTING.md
  • 3f2b104 Add support for coverage metrics with nyc and coveralls. Coveralls integration will need to be turned on.
  • df6608d Merge pull request #332 from hildjj/lint
  • 73f5d1a Switch to let/const from var
  • bf025a8 Apply the Firefox eslint rules, minus the Firefox-specific plugins.
  • 8214089 Merge pull request #330 from ds300/fix/callback-stack
  • b87dfc8 update dist
  • 121d627 keep callbacks on stack to allow nested consumer usage
  • b93aadb add failing test for nested consumer usage
  • c1e2ec8 Merge pull request #329 from wizawu/master

There are 16 commits in total.

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 sinon is breaking the build 🚨

Version 1.17.7 of sinon just got published.

Branch Build failing 🚨
Dependency sinon
Current Version 1.17.6
Type devDependency

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

As sinon 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 failed Details
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 🌴

Version Number issue

Hi, I noticed that recently you upgraded the node requirement for brolog to node 16.
In 1.12.4 there was no node version requirement. I think it is a breaking change, as it caused some node 10 apps breaking down when publishing new packages.

Brolog as a EventEmitter

For the maximum flexibility for the end-users for displaying the log messages, we plan to emit the log message as an event named loglevel.

For example:

log.on('verbose', (module, method, message) => {
  // filter module & method at here, and output whatever you want.
})

See: wechaty/puppet-service#152

An in-range update of magic-string is breaking the build 🚨

Version 0.24.1 of magic-string was just published.

Branch Build failing 🚨
Dependency magic-string
Current Version 0.24.0
Type devDependency

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

magic-string 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
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 ts-node is breaking the build 🚨

Version 7.0.1 of ts-node was just published.

Branch Build failing 🚨
Dependency ts-node
Current Version 7.0.0
Type devDependency

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

ts-node 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).
  • ❌ Travis CI - Branch: The build failed.
Release Notes Strip TypeScript "composite" flag

Added

  • Strip TypeScript composite flag from configuration file
Commits

The new version differs by 7 commits.

  • ad6183a 7.0.1
  • 6df09a9 Remove composite option from configuration (#657)
  • 2017b3a Ignore TypeScript error 2355 in REPL (#645)
  • 743e80f Add documentation for fixing missing types (#627)
  • 55741b6 Note defaults, ignoring node_modules, types tip
  • ff8ed42 Use argv defaults consistently
  • c692f94 Test custom typeRoots support in tsconfig.json

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 🌴

`log.info(Date())` is different with `console.log(Date())`

code as follows:

const date = "2017-10-19"
console.log(new Date(date + ' ' + '00:00:00'))
log.info(`${new Date(date + ' ' + '00:00:00')}`)

result:

2017-10-18T16:00:00.000Z
14:00:21 INFO Thu Oct 19 2017 00:00:00 GMT+0800 (CST)

I wonder to know why the result of console.log() and log.info() are different, or it is designed to this, and how can I use log.info() get the result as console.log() ?

Thanks

An in-range update of @types/puppeteer is breaking the build 🚨

Version 1.6.0 of @types/puppeteer was just published.

Branch Build failing 🚨
Dependency @types/puppeteer
Current Version 1.5.1
Type devDependency

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

@types/puppeteer 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).
  • ❌ Travis CI - Branch: The build failed.
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 semver is breaking the build 🚨

Version 5.5.1 of semver was just published.

Branch Build failing 🚨
Dependency semver
Current Version 5.5.0
Type devDependency

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

semver 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 passed (Details).
  • ❌ Travis CI - Branch: The build failed.
Commits

The new version differs by 5 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 ts-node is breaking the build 🚨

Version 6.0.4 of ts-node was just published.

Branch Build failing 🚨
Dependency ts-node
Current Version 6.0.3
Type devDependency

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

ts-node 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 Windows Project Resolution

Fixed

  • Normalize paths for Windows before trying to resolve the project path
  • Use Buffer.from instead of deprecated new Buffer
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 @types/sinon-test is breaking the build 🚨

Version 1.0.5 of @types/sinon-test was just published.

Branch Build failing 🚨
Dependency @types/sinon-test
Current Version 1.0.4
Type devDependency

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

@types/sinon-test 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
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 sinon is breaking the build 🚨

Version 5.0.8 of sinon was just published.

Branch Build failing 🚨
Dependency sinon
Current Version 5.0.7
Type devDependency

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

sinon 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
Commits

The new version differs by 12 commits.

  • 3685ee4 Update docs/changelog.md and set new release id in docs/_config.yml
  • 6b5d7fb Add release documentation for v5.0.8
  • 94f9264 5.0.8
  • be117c7 Update History.md and AUTHORS for new release
  • 9c64c8f Merge pull request #1803 from jdalton/is-es-module.js
  • 5983a6d Add isSealed check to is-es-module.
  • e2c7132 Update markdownlint-cli
  • 082f8e8 Update dependencies to appropriate semver-minor versions
  • a321764 Fix sandbox documentation
  • b578cf7 Update insecure dependencies
  • 96b7cad Update issue templates
  • ec00981 Typo'd fake to fakes

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 🌴

Enable logging with winston

Winston format: Winston.info('Hello %s!', 'world')

Brolog format: Brolog.info('Main', 'Hello %s!', 'world')

So we need to transform the arguments from Brolog to Winston if we use Brolog.enableLogging() with Winston.

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

Version 9.0.3 of tap just got published.

Branch Build failing 🚨
Dependency tap
Current Version 9.0.2
Type devDependency

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

As tap 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 failed Details
Commits

The new version differs by 3 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 jasmine-spec-reporter is breaking the build 🚨

Version 3.1.0 of jasmine-spec-reporter just got published.

Branch Build failing 🚨
Dependency jasmine-spec-reporter
Current Version 3.0.0
Type devDependency

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

As jasmine-spec-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/travis-ci/push The Travis CI build failed Details
Release Notes v3.1.0
  • Add displaySpecErrorMessages and displaySummaryErrorMessages to DisplayProcessor #85
  • Add an option to remove error messages #62
  • Add an option to customize stacktrace filtering #72
Commits

The new version differs by 11 commits .

  • a4e8aef 3.1.0
  • 8364f45 Update CHANGELOG.md
  • e2b4908 Add an option to customize stacktrace filtering #72
  • b26308c Add an option to remove error messages #62
  • 9ce8d2d Update colors and node types
  • 878fc63 Update CHANGELOG.md
  • 0530ee2 An alternate method for configuring for jasmine/node
  • 10c1d8a Update tslint and use latest rules.
  • 6e1653e Add displaySpecErrorMessages and displaySummaryErrorMessages to DisplayProcessor #85
  • 56e38e4 Extract process function #85
  • 320bc6a Rename typings property yo types

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 🌴

Compatible problem with Angular 4 AOT & WebPack

This is the reason that Brolog upgrade from v0.4 to v1.0.

You need to tell Typescript to emit CommonJS, not UMD. UMD is doing funky stuff with the require function, passing it as an argument into factory. This means webpack can't look at all usages of the top-level require function and figure out exactly what modules you're loading.
The require inside of factory is an argument, so it's different from the top-level require. They have the same name, but that's just a coincidence and webpack's static analysis knows they're not the same variable. (They store the same value at runtime, but static analysis can't figure that out)

See:
https://www.reddit.com/r/typescript/comments/4q09uv/help_webpack_weirdness_require_function_is_used/

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper 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 it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of jasmine-spec-reporter is breaking the build 🚨

Version 3.2.0 of jasmine-spec-reporter just got published.

Branch Build failing 🚨
Dependency jasmine-spec-reporter
Current Version 3.1.0
Type devDependency

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

As jasmine-spec-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/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 10 commits .

  • a296db0 3.2.0
  • 05be5de Update CHANGELOG.md
  • ce80e4b Update dependencies
  • 4cd3d66 chore(package): update jasmine to version 2.5.3
  • a1a0745 Add jasmine & protractor integration tests #82
  • 13f8da9 Add an option to remove duration from execution summary
  • 9b2635e Examples use same dependencies than project
  • baaf103 clean package.json scripts
  • 6847e2a chore(package): update typescript to version 2.1.5
  • 9b3d716 Make coverage work with typescript sources #83

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 @types/node is breaking the build 🚨

Version 10.5.4 of @types/node was just published.

Branch Build failing 🚨
Dependency @types/node
Current Version 10.5.3
Type devDependency

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

@types/node 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 passed (Details).
  • ❌ Travis CI - Branch: The build failed.
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 protractor is breaking the build 🚨

Version 4.0.14 of protractor just got published.

Branch Build failing 🚨
Dependency protractor
Current Version 4.0.13
Type devDependency

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

As protractor 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 failed Details
Commits

The new version differs by 17 commits .

  • 8952eab chore(release): Version bump and changelog for 4.0.14
  • 688f5d6 deps(update): update vrsource-tslint-rules and webdriver-manager (#3856)
  • c437fd3 deps(selenium-webdriver): clean up types selenium-webdriver (#3854)
  • 989759a chore(tslint): add tslint to gulpfile (#3833)
  • 075a512 chore(error): improve error message for local and direct driver providers (#3850)
  • 83694f5 fix(types): update for selenium-webdriver types creating transpile errors (#3848)
  • 41b5a19 chore(docs): add test app link to issue template (#3843)
  • ea09be4 fix(jasmine): Return the full test name in Jasmine test results. (#3842)
  • c9fad62 tests(element): We can now pass elements to executeScript. (#3844)
  • 2e6c1be docs(locators): add $$ shortcut to locators.md (#3845)
  • 2a8c252 chore(docs): fixes grammar issue in page title (#3821)
  • 2cf2453 chore(repo): organize ignore files (#3841)
  • 76cb4b4 fix(element): Fix typing of then function (#3785)
  • 5a12d69 fix(config): cucumberOpts.require should be an optional Array of strings (#3817)
  • b337a8e feat(config): add seleniumServerStartTimeout (#3791)

There are 17 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.63.5 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.63.4
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 passed (Details).
  • ❌ Travis CI - Branch: The build failed.
Commits

The new version differs by 11 commits.

  • dc9f347 0.63.5
  • 6c1d1e6 Fix typings for turbo color
  • e109576 Update changelog
  • 115239f Update changelog
  • da97ea5 Add plugin implemenation type (#2355)
  • 55d90d8 fix regression #2305, ensure onwrite plugin hooks execute in sequence (#2364)
  • fc1e6f7 Update changelog
  • d07d5bf Always warn when no name is provided for a global module (#2359)
  • 489477d Update changelog
  • 9eaa1d9 Remove "es6" output format from types (#2349)
  • 382323a fix(types): inlineDynamicImports is optional (#2348)

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 @types/sinon is breaking the build 🚨

Version 5.0.2 of @types/sinon was just published.

Branch Build failing 🚨
Dependency @types/sinon
Current Version 5.0.1
Type devDependency

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

@types/sinon 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 passed (Details).
  • ❌ Travis CI - Branch: The build failed.
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 @types/node is breaking the build 🚨

Version 10.0.9 of @types/node was just published.

Branch Build failing 🚨
Dependency @types/node
Current Version 10.0.8
Type devDependency

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

@types/node 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
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 🌴

Browser support had broken for behavior change of rollup.

See: rollup/rollup#1750

Workaround: output.extend = true

output.extend --extend/--no-extend*
true or false (defaults to false) – whether or not to extend the global variable defined by the name option in umd or iife formats. When true, the global variable will be defined as (global.name = global.name || {}). When false, the global defined by name will be overwritten like (global.name = {}).

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

Version 2.3.1 of rollup-plugin-json was just published.

Branch Build failing 🚨
Dependency rollup-plugin-json
Current Version 2.3.0
Type devDependency

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

rollup-plugin-json 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
Commits

The new version differs by 7 commits.

  • 50db997 2.3.1
  • 1cbc065 Update changelog
  • c204154 Merge branch 'nebulousdog-some-options-renamed'
  • b33e267 Produce a warning when installing this version alongside rollup 0.59+
  • 0cf87fd Produce a warning when installing this version alongside rollup 0.59+
  • 39c5119 updates README example with updated options names
  • 585fe3d ugh node 4

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

Need method to check the level

Hi Huan,

I'd like to be able to do this:

if (brolog.getLevel() === 'verbose') {
    // do some debugging
}

What do you think about that addition?

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.