Code Monkey home page Code Monkey logo

node-v's Introduction

V Logo

🔒 Secure ❄️ Synchronized ⚡️ Realtime ☁️ Cloud 🌈 Native JavaScript Variables & Events

npm downloads Greenkeeper badge Build Status codecov
NSP Status Known Vulnerabilities

V extends your in-memory variables to also be saved/persisted instantly. Variables are instantly synchronized between all running instances of V in a room. When you (re)start in a room, variables and constants are reloaded/rehydrated automatically.

Current Features

  • Keep your variables in the cloud
  • Sync variables between instances
  • Automatic reloaded/rehydrated on start-up

Requires ES6 Proxy (Node 6+ and new browsers)

Coming Soon:

  • Web GUI
  • History - Time machine
  • Events pub/sub

Install

Node

npm install --save v
or
npm i -S v

Browser

jsDelivr CDN:

<script src="https://cdn.jsdelivr.net/npm/v@latest/v.min.js"></script>

Unpkg CDN:

<script src="https://unpkg.com/v/v.min.js"></script>

More CDNs coming soon

API

Constructor (3 Ways to do it)

If no roomId is passed, a new one will be assigned automatically and printed in the console.

NodeJS only with deasync support
const V = require('v')
const v = new V([roomId])
Callback
const V = require('v')
V([roomId,] v => {
  ...
})
Promise
const V = require('v')
V([roomId]).then(v => {
  ...
}).catch(e => {
  ...
})

Custom Opts

The opts object has the following options and their default options listed

myOpts = {
  roomId: '',
  server: 'ws(s)://my-domain.com'
}

Use it:

const v = new V(myOpts)

Debug logs

V comes with extensive debugging logs. Each V instance and constructor-call has it own debug namespace.

In node, enable debug logs by setting the DEBUG environment variable to *

DEBUG=* node myProgram.js

In the browser, enable debug logs by running this in the developer console:

localStorage.debug = '*'

Disable by running this:

localStorage.removeItem('debug')

License

MIT Copyright © Diego Rodríguez Baquero

node-v's People

Contributors

diegorbaquero avatar fabioespinosa avatar greenkeeper[bot] avatar klosorio10 avatar lukasdrgon avatar

Stargazers

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

Watchers

 avatar  avatar  avatar  avatar  avatar

node-v's Issues

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

Version 15.1.0 of browserify was just published.

Branch Build failing 🚨
Dependency browserify
Current Version 15.0.0
Type devDependency

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

browserify 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.0
  • restore support for node < 4.0 until we can decide on a support schedule
Commits

The new version differs by 8 commits.

  • 6dbd142 15.1.0
  • 00f226b changelog
  • c668b99 Merge pull request #1794 from ljharb/restore_old_node
  • a522c43 Set engines back to 0.8 (reverts #1793)
  • 2ab8502 [Tests] skip template literal tests unless supported
  • 7a6116c [Tests] skip generator tests in nodes that don’t support generators
  • ea84e09 [Deps] upgrade module-deps
  • 1d5ebb6 [Tests] start testing in older nodes again

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

Version 2.0.4 of bogota just got published.

Branch Build failing 🚨
Dependency bogota
Current Version 2.0.3
Type devDependency

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

As bogota 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 is in progress Details

  • bitHound - Dependencies 1 failing dependency. Details

  • bitHound - Code No failing files. Details

Commits

The new version differs by 8 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 🚨

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

Version 11.6.0 of nyc was just published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.5.0
Type devDependency

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

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

  • dd372f5 chore(release): 11.6.0
  • c6b30ba feat: allow usage of ignoreClassMethods from istanbul (#785)
  • 2d51562 fix: update to yargs version that allows extending configs with no extension (#790)
  • b4032ce fix: removes unused split-lines dependency. (#787)

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

Version 0.1.12 of deasync was just published.

Branch Build failing 🚨
Dependency deasync
Current Version 0.1.11
Type optionalDependency

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

deasync is a optionalDependency 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 1 commits.

  • 3638d54 replaced _tickDomainCallback with _tickCallback

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

Version 2.3.1 of codecov was just published.

Branch Build failing 🚨
Dependency codecov
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.

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

Version 0.1.11 of deasync was just published.

Branch Build failing 🚨
Dependency deasync
Current Version 0.1.10
Type optionalDependency

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

deasync is a optionalDependency 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 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 nyc is breaking the build 🚨

Version 11.4.1 of nyc was just published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.4.0
Type devDependency

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

nyc 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 3 commits.

  • b473820 chore(release): 11.4.1
  • 4e4f428 fix: explicitly update spawn-wrap (#748)
  • 456fa20 docs: hide the header in the issue template on render [skip ci] (#731)

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

Version 5.1.0 of simple-websocket was just published.

Branch Build failing 🚨
Dependency simple-websocket
Current Version 5.0.2
Type dependency

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

simple-websocket is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed 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.3.0 of nyc was just published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.2.1
Type devDependency

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

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

  • d85118c chore(release): 11.3.0
  • 7792733 chore: explicitly update istanbul dependencies (#698)
  • 222a3d0 chore: slight difference in pinning logic, based on @ljharb's advice
  • f04b7a9 feat: add option to hook vm.runInContext (#680)
  • cdfdff3 feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
  • a413f6a chore: upgrade to yargs 10 (#694)
  • 10125aa docs: fix reporters link
  • f5089ca docs: added examples of coverage reports (#656)
  • af281e7 chore: update spawn-wrap to 1.4.0 (#692)
  • a685f7c docs: missing options prefix -- in front of check-coverage (#695)
  • f31d7a6 feat: allow instrument-only to produce sourcemaps (#674)
  • 425c0fd chore: ignore package-lock.json (#683)

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

Version 14.2.0 of browserify just got published.

Branch Build failing 🚨
Dependency browserify
Current Version 14.1.0
Type devDependency

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

As browserify 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 No failing files. Details

  • bitHound - Dependencies No failing dependencies. Details

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

Commits

The new version differs by 5 commits .

  • 18e1d65 14.2.0
  • 0e1a7a0 add cli support for --transform-key to support mode's like production/staging/etc..
  • a5aa660 Merge pull request #1701 from wogsland/doc-fix
  • ae281bc Fixed documentation formatting that was bugging me
  • fe8c57b async test for node 7

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

Version 5.1.1 of simple-websocket was just published.

Branch Build failing 🚨
Dependency simple-websocket
Current Version 5.1.0
Type dependency

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

simple-websocket is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

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

Commits

The new version differs by 4 commits.

  • 3f1ddfa build
  • f5bdead 5.1.1
  • cd1ae84 Merge pull request #26 from jhiesey/master
  • 2d02514 Swallow errors after _destroy() instead of letting them crash the process

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

Version 4.9.0 of tape was just published.

Branch Build failing 🚨
Dependency tape
Current Version 4.8.0
Type devDependency

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

tape 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 27 commits.

  • ea6d91e v4.9.0
  • 6867840 [Deps] update object-inspect, resolve
  • 4919e40 [Tests] on node v9; use nvm install-latest-npm
  • f26375c Merge pull request #420 from inadarei/global-depth-env-var
  • 17276d7 [New] use process.env.NODE_TAPE_OBJECT_PRINT_DEPTH for the default object print depth.
  • 0e870c6 Merge pull request #408 from johnhenry/feature/on-failure
  • 00aa133 Add "onFinish" listener to test harness.
  • 0e68b2d [Dev Deps] update js-yaml
  • 10b7dcd [Fix] fix stack where actual is falsy
  • 13173a5 Merge pull request #402 from nhamer/stack_strip
  • f90e487 normalize path separators in stacks
  • b66f8f8 [Deps] update function-bind
  • cc69501 Merge pull request #387 from fongandrew/master
  • bf5a750 Handle spaces in path name for setting file, line no
  • 3c2087a Test name with spaces

There are 27 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 simple-websocket is breaking the build 🚨

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

Version 7.0.2 of simple-websocket was just published.

Branch Build failing 🚨
Dependency simple-websocket
Current Version 7.0.1
Type dependency

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

simple-websocket is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed 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 browserify is breaking the build 🚨

Version 14.5.0 of browserify was just published.

Branch Build failing 🚨
Dependency browserify
Current Version 14.4.0
Type devDependency

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

browserify 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 9 commits.

  • ccc0213 14.5.0
  • f2e720a changelog 14.5.0
  • 37bd7b4 Merge pull request #1733 from dignifiedquire/patch-1
  • 5a0c9ac use ~ range for <v1.0 deps
  • 866a2e7 Merge pull request #1767 from amiller-gh/master
  • 9857f90 Update os-browserify to 0.3.0
  • 0305b70 update readme links and travis badge
  • 9bc05a3 code of conduct
  • 52c0856 bump browserify-zlib to 0.2.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 browserify is breaking the build 🚨

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

Version 16.1.1 of browserify was just published.

Branch Build failing 🚨
Dependency browserify
Current Version 16.1.0
Type devDependency

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

browserify 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 9 commits.

  • 25c71db 16.1.1
  • fa00040 Merge pull request #1815 from browserify/ignore-perf-hooks
  • a3a3e9c ignore perf_hooks
  • 99f86dc Merge pull request #1811 from browserify/node-0.10-tests
  • 8bbddf7 Merge pull request #1810 from al-k21/bare-fix
  • d430656 explicitly mention to use ./ in require() for local files, closes #1774
  • 989cc56 Fix tests on Node <0.10
  • 1ab192c test/bare.js: nits
  • 680d0e6 test/bare.js: fix file path

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.