Giter VIP home page Giter VIP logo

pouchy's Introduction

pouchy

"Pouchy is the sugar API for PouchDB that I've been hoping someone would write" @nolanlawson

JavaScript Style Guide semantic-release CircleCI Coverage Status TypeScript package

NPM

simple, enhanced PouchDB. Pouchy wraps & extends PouchDB and provides various sorely needed sugar methods. further, it assists by standardizing the returned document format. most methods provided are very simple PouchDB-native method modifiers, but are targeted to save you frequent boilerplate re-typing! this library also proxies the PouchDB API directly, so you can use it like a PouchDB instance itself!

install

yarn add pouchy

if you need node support to flush databases to disk, versus using pouchy as an api client to remote couch/pouches, add your preferred adapters too. e.g.:

yarn add pouchy pouchdb-adapter-leveldb

usage

api docs and examples officially live here.

here are some basic examples:

// local, node database
import Pouchy from 'pouchy'
import level from 'pouchdb-adapter-leveldb'
Pouchy.plugin(level)
type Fruit = { type: string, tastes: string }
const fruit = new Pouchy<Fruit>({ name: 'fruit' })
const orange = await fruit.save({ type: 'orange', tastes: 'delicious' })
console.log(orange)

/**
  {
    type: 'orange',
    tastes: 'delicious',
    _id: 'EA1F2B55-2482-89C6-907E-6F938C59F734',
    _rev: '1-f60b9b7d775a89d280e1f4c07122b863'
  }
*/
// local & remote replicated database!
import Pouchy from 'pouchy'
import memory from 'pouchdb-adapter-memory'
Pouchy.plugin(memory)

const customers = new Pouchy({
  name: 'customers',
  replicate: 'sync',
  url: 'http://mydomain.org/db/customers'
})
customers.save({ firstName: 'bill', lastName: 'brasky' })
// wait for it... and couchdb/pouchdb-server @ http://mydomain.org/db/customers
// will receive bill brasky!

why

why use pouchy over pouchdb?

  • because managing _id and _rev can be obnoxious with pouchdb (no hard feelings, of course).
    • pouchdb methods return document _ids and _revs inconsistently. some methods return docs with an id attribute. some return docs with _id. the same happens for rev.
    • different methods return _rev nested under other attributes, vs. being at the top of the document.
    • pouchy lets you get your documents back in the same way they are represented in the store. if you are expecting an _id and a _rev in a return result, you'll get those attributes back on the top of your documents, every time.
  • because you need some frequently used sugar methods that aren't keys-included from pouchdb. there are many sugar methods available, make sure to check out the API docs!
    • e.g. .all(), to get all full documents in your store, in a simple array.
    • e.g. .clear()/.deleteAll() to purge your store of its docs.
  • because you want .find to return simply an array of docs!
    • note: pouchy pre-loads the pouchdb-find plugin, which is super handy and regularly recommended for use.
  • because you want to pre-define *ouchdb synchronization behavior on construction! start syncing pronto, declaratively!

Thanks! cdaringe

changelog

  • 12.3.+ - switched to semantic-release. please view the "Releases" GitHub tab
  • 12.0.0
    • refactor all of the things!
      • better handle all rev/id ==> _rev/_id mapping
      • if rev or id exist on docs returned from pouch exist, but no _rev or _id exist, that particular kv pair will be moved to the _-prefixed key and the non prefixed key will be removed.
    • more tests!
  • 11.0.2
    • drop es6 content. es5 friendly-ify!
  • 11.0.0
    • pouchdb 6.0.5!
  • 10.1.0
    • expose replication options via getReplicationOptions
    • on destroy, actually destroy gracefully. that means, don't resolve the promise/callback until live dbs have all http requests fully settled. see here for more info.
  • 10.0.4 - be compatible with latest bluebird .asCallback.
  • 10.0.0 - migrate to PouchDB 5.4.x. @NOTE, some APIs are not available by default anymore. See the custom build blog post on how to add features to your pouch Pouchy.PouchDB.plugin(...). The following plugins are available by default:
    • pouchdb-adapter-http
    • pouchdb-find
    • pouchdb-replication
  • 9.0.2 - fix bulkGet when no docs are provided
  • 9.0.0-1
    • fix .all({ include_docs: false }) to properly handle .rev/._rev
    • improve docs!
  • 8.0.5 - fix issues w/ promise/cbs. sorry for 8.0.x-8.0.5 churn!
  • 8.0.0 - support cb & promise interface. added bluebird to make this seamless and less verbose
  • 7.1.0 - add hasLikelySynced event
  • 7.0.0 - modify replicate API. dropped 'both' sync option, added {} option. dropped replicateLive
  • 6.3.0 - add destroy, which .cancels any replication from .syncEmitter (see replicate). deprecate 6.2.0-1. changeEmitter => syncEmitter (rapid patch, so no major bump)
  • 6.2.1 - add this.syncEmitter when using the replicate API
  • 6.1.0 - add bulkGet
  • 6.0.6 - fix issue where _id was still id when doing .all({ include_docs: false })
  • 6.0.4 - fix replication issue where db backend not honored
  • 6.0.0 - db will store locally via leveldown as name if passed. url will still be used for replication if requested. prior versions preferred url to the Pouch constructor over name
  • 5.2.1 - permit / in couchdb db name
  • 5.2.0 - bump with couch
  • 5.1.0 - deps bump & add cb interface
  • 5.0.0 - deps bump only. all future releases with track major version #s with PouchDB
  • 4.0.0 - major bump with PouchDB
  • 3.0.0 - remove default changes, and associated on/off. didn't work out-of-the-box anyway. may return in 4.x
  • 2.0.1 - Don't modify constructor opts.name
  • 2.0.0 - Fix synced db fs location. Previously was not honoring path option
  • 1.0.0 - 2.0.1 pouchdb-wrapper => pouchy

pouchy's People

Contributors

cdaringe avatar greenkeeper[bot] avatar greenkeeperio-bot avatar renovate-bot avatar snyk-support avatar tabrindle avatar wa11-e 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  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  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

pouchy's Issues

Is this project active?

Hi all.

I want to help, but I want to know if this project is active. Is this project active?

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

The dependency snyk was updated from 1.179.0 to 1.179.1.

🚨 View failing branch.

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

snyk 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v1.179.1

1.179.1 (2019-06-20)

Bug Fixes

  • name and version in gomodules (7cbc9e1)
Commits

The new version differs by 2 commits.

  • de94535 Merge pull request #583 from snyk/fix/gomodules-name-version
  • 7cbc9e1 fix: name and version in gomodules

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

The devDependency husky was updated from 3.0.1 to 3.0.2.

🚨 View failing branch.

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

husky 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v3.0.2
  • Fix: add shebang to run.js (#528)
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 🌴

Docs: mention the steps needed to get indexedDB working

Hi!
Continuing this.
I personally came to PouchDB and then Pouchy because I needed an abstaction over IndexedDB api.
In my understanding, PouchDB was initially created to provide this very api; and then it evolved into smth bigger. Maybe it's wrong understanding.
So.. it was only reasonable to expect Pouchy to work with IndexedDB out of the box. It took me quite some time to figure the adaptor stuff out, by also scanning through closed issues here.
Therefore, I would ask you to explicitly mention steps needed to get going with IndexedDB. In the Guide or Getting started section of the docs. Thx.

An in-range update of gh-pages is breaking the build 🚨

The devDependency gh-pages was updated from 2.0.1 to 2.1.0.

🚨 View failing branch.

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

gh-pages 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Commits

The new version differs by 9 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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because 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 delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

'A module cannot import itself' error when bundling pouchdb-adapter-websql & Pouchy with Rollup

Issue

This was crosspost to PouchDB - pouchdb/pouchdb#6345

There seems to be a new bug between PouchDB release 6.1.1 and 6.1.2 where the websql adapter will cause rollup to crash while bundling with Pouchy.

A module cannot import itself (/Users/tabrindle/Developer/media-hybrid/node_modules/pouchdb-adapter-websql/node_modules/pouchdb-utils/lib/index-browser.es.js)
Error: A module cannot import itself (/Users/tabrindle/Developer/media-hybrid/node_modules/pouchdb-adapter-websql/node_modules/pouchdb-utils/lib/index-browser.es.js)
    at /Users/tabrindle/Developer/media-hybrid/node_modules/rollup/src/Bundle.js:335:14

The error suggests this is the culprit: import { nextTick } from 'pouchdb-utils'; from inside pouchdb-utils/lib/index-browser.es.js

This file is not present in 6.1.1.

Here is my rollup config:

import resolve from 'rollup-plugin-node-resolve';
import commonjs from 'rollup-plugin-commonjs';
import uglify from 'rollup-plugin-uglify';
import builtins from 'rollup-plugin-node-builtins';
import globals from 'rollup-plugin-node-globals';
import { minify } from 'uglify-js';

export default {
    entry: 'resources/libs/index-rollup.js',
    dest: 'resources/libs/bundle.js',
    format: 'iife',
    moduleName: 'bundle',
    plugins: [
        builtins(),
        resolve({
            jsnext: true,
            main: true,
            browser: true,
            preferBuiltins: false
        }),
        commonjs({
            include: 'node_modules/**'
        }),
        globals(),
        uglify({
            compress: {
               unused: false
            }
        }, minify)
    ]
};

Based on the resolves I have configured, I realize that rollup will select this new file over the old, but what I dont understand is why rollup has an issue with it.

Just a shot in the dark, I'm guessing this may have to do with @nolanlawson 's pulls #6162 (Make polyfills extractable) or #6170 (dont expost src to npm) based on the commit logs to these files, and the changelog from this release.

This may not actually be a bug, just an unintended side effect of how I am using the package - Of note, I am using Pouchy 11.0.3, which uses pouchdb-core 6.0.6. Will also crosspost this issue to Pouchy.

Info

  • Environment: Node.js v6.10.0
  • Adapter: WebSQL

Reproduce

Install Pouchy 11.0.3 and [email protected] and attempt to bundle them with rollup

Can't find variable: Buffer

I'm trying to have Pouchy work with SQlite on an Expo/react-native app but with no success.

import Expo, { SQLite } from "expo";
import SQLiteAdapterFactory from "pouchdb-adapter-react-native-sqlite";
const Pouchy = require('pouchy')
const SQLiteAdapter = SQLiteAdapterFactory(SQLite);
Pouchy.plugin(SQLiteAdapter);

const fruit = new Pouchy({ name: "fruit" });
    fruit
      .save({ type: "orange", tastes: "delicious" })
      .then(orange => console.log(orange));

simulator screen shot

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

There have been updates to the pouchdb monorepo:

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the pouchdb group definition.

pouchdb 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
  • ci/circleci: build: Your tests failed on CircleCI (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 standard is breaking the build 🚨

The devDependency standard was updated from 13.1.0 to 14.0.0-1.

🚨 View failing branch.

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

standard 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Commits

The new version differs by 70 commits.

  • 7117e53 14.0.0-1
  • c1ebec6 Disallow spaces inside of curly braces in JSX expressions in children (react/jsx-curly-spacing)
  • 2d619f3 Require linebreaks in curly braces in JSX attributes and expressions to be consistent (react/jsx-curly-newline)
  • 5dfdc83 Require JSX event handler names to follow conventions (react/jsx-handler-names)
  • ff4ef49 Require JSX attributes and logical expressions to be indented correctly (react/jsx-indent)
  • 13e4bee Disallow missing key prop in JSX elements that likely require a key prop (react/jsx-key)
  • 29861dc Disallow accidental comments in JSX from being inserted as text nodes (react/jsx-no-comment-textnodes)
  • c852a11 Prevent usage of unsafe target='_blank' (react/jsx-no-target-blank)
  • 30eddfa Disallow unnecessary curly braces in JSX props and children. (react/jsx-curly-brace-presence)
  • d3d14a5 Require PascalCase for user-defined JSX components (react/jsx-pascal-case)
  • 93027d9 Require shorthand form for JSX fragments (react/jsx-fragments)
  • 093b7f0 Disallow multiple spaces between inline JSX props (react/jsx-props-no-multi-spaces)
  • 6ee9fb1 alphabetize rules
  • d179362 remove rule which already shipped
  • f8551e9 Require JSX closing bracket to be aligned with the opening tag (react/jsx-closing-bracket-location)

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

The devDependency browserify was updated from 16.3.0 to 16.4.0.

🚨 View failing branch.

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
  • ci/circleci: build: Your tests failed on CircleCI (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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because 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 delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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

The devDependency semantic-release was updated from 15.13.18 to 15.13.19.

🚨 View failing branch.

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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v15.13.19

15.13.19 (2019-07-06)

Bug Fixes

  • package: update marked to version 0.7.0 (75f0830)
Commits

The new version differs by 3 commits.

  • 75f0830 fix(package): update marked to version 0.7.0
  • 4b2b2fb chore(package): update clear-module to version 4.0.0
  • 3b8cae9 docs: fix typo

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

The devDependency @types/lodash was updated from 4.14.136 to 4.14.137.

🚨 View failing branch.

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

@types/lodash 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
  • ci/circleci: build: Your tests failed on CircleCI (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 🌴

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • chore(deps): replace dependency npm-run-all with npm-run-all2 5.0.0
  • chore(deps): update dependency @types/blue-tape to v0.1.36
  • chore(deps): update dependency @types/bluebird to v3.5.42
  • chore(deps): update dependency @types/pouchdb to v6.4.2
  • chore(deps): update dependency @types/pouchdb-adapter-leveldb to v6.1.6
  • chore(deps): update dependency @types/tape to v4.13.4
  • fix(deps): update dependency lodash to v4.17.21
  • fix(deps): update dependency url to v0.11.3
  • fix(deps): update dependency bluebird to v3.7.2
  • fix(deps): update pouchdb monorepo to v7.3.1 (pouchdb-adapter-http, pouchdb-adapter-leveldb, pouchdb-adapter-memory, pouchdb-core, pouchdb-find, pouchdb-replication)
  • chore(deps): update dependency fs-extra to v11 (fs-extra, @types/fs-extra)
  • chore(deps): update dependency husky to v9
  • chore(deps): update dependency lint-staged to v15
  • chore(deps): update dependency typescript to v5
  • chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
  • fix(deps): update pouchdb monorepo to v8 (major) (pouchdb-adapter-http, pouchdb-adapter-leveldb, pouchdb-adapter-memory, pouchdb-core, pouchdb-find, pouchdb-replication)
  • 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

npm
package.json
  • bluebird ^3.5.3
  • lodash ^4.17.4
  • path 0.12.7
  • pouchdb-adapter-http ^7.0.0
  • pouchdb-core ^7.0.0
  • pouchdb-find ^7.0.0
  • pouchdb-replication ^7.0.0
  • url 0.11.0
  • @babel/core 7.14.6
  • @babel/polyfill 7.12.1
  • @babel/preset-env 7.14.7
  • @types/blue-tape 0.1.33
  • @types/bluebird 3.5.36
  • @types/fs-extra 9.0.12
  • @types/lodash 4.14.171
  • @types/pouchdb 6.4.0
  • @types/pouchdb-adapter-leveldb 6.1.3
  • @types/tape 4.13.1
  • @typescript-eslint/eslint-plugin 4.28.2
  • @typescript-eslint/parser 4.28.2
  • babelify 10.0.0
  • blue-tape 1.0.0
  • browserify 17.0.0
  • coveralls 3.1.1
  • eslint-plugin-typescript 0.14.0
  • fs-extra 10.0.0
  • gh-pages 3.2.3
  • husky 7.0.1
  • jsdock 1.0.4
  • lint-staged 11.0.0
  • npm-run-all 4.1.5
  • nyc 15.1.0
  • perish 1.0.3
  • pouchdb-adapter-leveldb 7.2.2
  • pouchdb-adapter-memory 7.2.2
  • pouchdb-adapter-websql 7.0.0
  • prettier-standard 16.4.1
  • semantic-release 17.4.4
  • snyk 1.657.0
  • spawn-pouchdb-server 3.3.3
  • standardx 7.0.0
  • tape 5.2.2
  • testem 3.4.2
  • typedoc 0.21.2
  • typedoc-plugin-external-module-name 4.0.6
  • typescript 4.3.5
nvm
.nvmrc

  • Check this box to trigger a request for Renovate to run again on this repository

An in-range update of lint-staged is breaking the build 🚨

The devDependency lint-staged was updated from 8.1.0 to 8.1.1.

🚨 View failing branch.

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

lint-staged 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v8.1.1

8.1.1 (2019-01-28)

Bug Fixes

  • Fix configuration validation and allow specifying custom renderers (#572) (d5e738d), closes #567
Commits

The new version differs by 7 commits.

  • d5e738d fix: Fix configuration validation and allow specifying custom renderers (#572)
  • 406a0c0 chore: Revert "chore: pin cosmiconfig to 5.0.6" (#571)
  • adfc1d4 docs(readme): Add example for environment variables (#564)
  • 73e04d7 chore: Use unmock to get rid of mock hoisting (#563)
  • ac8cdf1 docs: Remove comment about hunks support (#553)
  • 352ab8c docs: Update for JetBrains support (#552)
  • 30576d6 chore: Upgrade semantic-release to latest (#548)

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 🌴

Cannot resolve dependency 'pouchy'

import Pouchy from 'pouchy'
Error: Cannot resolve dependency 'pouchy' when using parcel & typescript.
Happens on "pouchy": "^13.0.3".
On "pouchy": "^12.3.1" all is fine.

An in-range update of lint-staged is breaking the build 🚨

The devDependency lint-staged was updated from 9.2.0 to 9.2.1.

🚨 View failing branch.

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

lint-staged 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v9.2.1

9.2.1 (2019-07-25)

Bug Fixes

Commits

The new version differs by 13 commits.

  • e879b6a fix: pin [email protected] to support node 8
  • ee774e3 fix: pin [email protected] to support node 8
  • eb07cd5 chore: use jsonlint --in-place
  • 6126b72 fix: remove empty spaces from warning
  • 0ce85b2 chore: upgrade devDependencies and simplify eslint config
  • 34ab803 chore: upgrade production depedencies
  • 127cd95 refactor: set SIGINT listener in bin instead of runAll
  • 0342ebf test: update snapshots
  • 7a9df2f refactor: change 'linters' to 'tasks'
  • 7432469 test: add integration test for runAll
  • 8ba95d5 refactor: allow runAll and generateTasks to receive cwd
  • cf8a005 docs: add information about ignoring files
  • da0bbc7 docs: add --relative to README

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 🌴

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Invalid Adapter: undefined

Hi

I have a problem with webpack

On client:

const Pouchy = require('pouchy');
const db = new Pouchy({
        name: 'users',
        replicate: 'sync',
        url: ServerDefinition.ADDRESS + Collections.USERS
    });

screenshot from 2017-02-19 13 09 34

And this is my webpack config (part of)

const config = {
    entry:  {
        site      : APP_DIR + '/site/index.js',
        entrance  : APP_DIR + '/entrance/index.js',
        vendor    : [
            'pouchy',
            'pouchdb',
            'lodash'
        ]
    },
    output: {
        path: BUILD_DIR,
        filename: '[name].js'
    },
    resolve: {
        alias: {
            'vue$': 'vue/dist/vue.common.js'
            // semantic: path.resolve('./libs/semantic/dist/semantic.js')
        }
    },
    plugins: [
        new webpack.optimize.CommonsChunkPlugin({
            name: 'vendor', // Specify the common bundle's name.
            filename: "vendors.bundle.js"
        }),

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.