redgeoff / slouch Goto Github PK

View Code? Open in Web Editor NEW

121.0 3.0 24.0 435 KB

A JS client for CouchDB that does the heavy lifting

License: MIT License

JavaScript 98.92% Shell 1.08%

couchdb api js slouch node browser

slouch's Introduction

slouch

A JS API for CouchDB that does the heavy lifting

Slouch is a good alternative to nano:

You don't have to create an instance for each DB
Supports native promises
Supports iterators
Automatically throttles connections to DB to avoid max_dbs_open errors
Automatically persists connections with exponential backoff in case DB restarts or connection is dropped
Works in node and in the browser
Provides upserts and "get and update" functions
Support for optionally ignoring conflicts, missing docs, etc...
Designed for CouchDB 1, CouchDB 2 and CouchDB 3

slouch's People

Contributors

Stargazers

Watchers

slouch's Issues

An in-range update of wait-on is breaking the build 🚨

The devDependency wait-on was updated from `3.1.0` to `3.2.0`.

🚨 View failing branch.

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

wait-on 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: Your tests failed on CircleCI (Details).

Release Notes for v3.2.0

Added --tcpTimeout option

--tcpTimeout

Maximum time in ms for tcp connect, default 300ms

thanks @Sarithis

Commits

The new version differs by 3 commits.

31293af 3.2.0
813423e Merge pull request #32 from Sarithis/master
b32d023 Adds a tcp timeout. Fixes #31

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 🌴

Different approach for sending request body at create and update doc methods

Encountered an error using mock-couch as db server. The request body was missing, so I dig deeper and found out that you are using different body sending parameters.

CREATE uses "json: doc", UPDATE uses "JSON.stringify(doc), paraseBody: true"
check the image

When I "hack" the UPDATE method and send "json: doc", everything looks okay.

What are your thoughts on this?

Add URL encoding to DB names to support special characters

As mentioned in issue redgeoff/replicate-couchdb-cluster#42 replicate-couchdb-cluster isn't able to replicate CouchDBs with special cahracters due to a limitation of URL encoding CouchDB DB names in the slouch dependancy likely in this file https://github.com/redgeoff/replicate-couchdb-cluster/blob/master/scripts/cluster.js

It's likely that in addition to slashes, other special characters like + in DBs name are also problematic. URL encoding all DB names is likely to solve this problem.

Default timeout?

Should there be a default timeout so that if the request hangs on the CouchDB end, it will be eventually be considered dead and can be retried?

Add equivalent to `nano.db.list`

As it stands, there's no facility for listing all databases on a CouchDB server in slouch.

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

Version 4.1.2 of chai just got published.

Branch	Build failing 🚨
Dependency	chai
Current Version	4.1.1
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

❌ ci/circleci Your tests failed on CircleCI Details

Release Notes

4.1.2 / 2017-08-31

This release fixes a bug when running in certain environments, and includes a few minor documentation fixes.

Bug Fixes

fix: update deep-eql to version 3.0.0 (#1020)
fix: replace code causing breakage under strict CSP (#1032; @Alhadis)

Docs

docs: add missing assert parameters (#1017, #1023; @Hpauric)
docs: update year in license file (#1025; @yanca018)

Commits

The new version differs by 8 commits.

529d395 Merge pull request #1037 from Cutlery-Drawer/master
b534fca [email protected]
c592551 Merge pull request #1032 from Cutlery-Drawer/csp-fix
31c3559 Use a hardcoded no-op instead of instancing
1ae9386 Merge pull request #1025 from yanca018/master
786043b Update license
7c1ca16 docs: add missing assert parameters (#1023)
6e72c5a fix(package): update deep-eql to version 3.0.0 (#1020)

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 🚨

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

Version 5.0.2 of mocha was just published.

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

mocha 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 A command timed out during your tests Details

Release Notes

v5.0.2

5.0.2 / 2018-03-05

This release fixes a class of tests which report as false positives. Certain tests will now break, though they would have previously been reported as passing. Details below. Sorry for the inconvenience!

🐛 Fixes

#3226: Do not swallow errors that are thrown asynchronously from passing tests (@boneskull). Example:
```
it('should actually fail, sorry!', function (done) {
  // passing assertion
  assert(true === true);
// test complete & is marked as passing

done();
// ...but something evil lurks within

setTimeout(() => {

throw new Error('chaos!');

}, 100);

});
```
Previously to this version, Mocha would have silently swallowed the chaos! exception, and you wouldn't know. Well, now you know. Mocha cannot recover from this gracefully, so it will exit with a nonzero code.

Maintainers of external reporters: If a test of this class is encountered, the Runner instance will emit the end event twice; you may need to change your reporter to use runner.once('end') intead of runner.on('end').
#3093: Fix stack trace reformatting problem (@outsideris)

:nut_and_bolt Other

#3248: Update browser-stdout to v1.3.1 (@honzajavorek)

Commits

The new version differs by 13 commits.

f2ee53c Release v5.0.2
ff1bd9e update package-lock.json
6a796cb prepare CHANGELOG for v5.0.2 [ci skip]
0542c40 update README.md; closes #3191 [ci skip]
afcd08f add MAINTAINERS.md to .fossaignore [ci skip]
3792bef add opencollective header image to assets/
5078fc5 persist paths in stack trace which have cwd as infix
2c720a3 do not eat exceptions thrown asynchronously from passed tests; closes #3226
3537061 Update to correctly licensed browser-stdout version
ec8901a remove unused functionality in utils module
f71f347 rename wallaby.js -> .wallaby.js
c4ef568 fix PR url
73d55ac fix typos in changelog [ci skip]

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 🌴

Refactor logging in EnhancedRequest

Split into request and response entries with a "debug id" so that you can see when the request is made even if a response has not yet arrived
Add timestamps to the request and response logs

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

Version 5.0.1 of mocha was just published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	5.0.0
Type	devDependency

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

Status Details

❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 15 commits.

09ce746 Release v5.0.1
70027b6 update changelog for v5.0.1 [ci skip]
44aae9f add working wallaby config
412cf27 [Update] license year
b7377b3 rename help-wanted to "help wanted" in stale.yml
d975a6a fix memory leak when run in v8; closes #3119
3509029 update .gitignore to only ignore root mocha.js [ci skip]
b57f623 fix: When using --delay, .only() no longer works. Issue #1838
cd74322 Slight copy update on docs for test directory
f687d2b update docs for the glob
14fc030 Add all supported wallaby editors
2e7e4c0 rename "common-mistake" label to "faq"
bca57f4 clarify docs on html, xunit and 3p reporters; closes #1906
2fe2d01 Revert "fix travis "before script" script"
c0ac1b9 fix travis "before script" script

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 🌴

Run CouchDB on port 15984 instead of 5984 to prevent circleci bind conflicts

Can I ask you (redgeoff) a question?

Sorry, tried to find some means of contact but none found. I found slouch which could have been what I needed but it's not maintained as I see.

However, I really just have a very simple question that vexes me and I thought may be you could possibly want to share some knowledge regarding interacting with couchDB.

My issue is to have a webpage that is hosted on another domain and be able to log in and interact with several couchDB servers using cookie authentication. I have set the CORS to accept the domain of my webpage, and I have credentials: 'include' in the header but I still get unauthorised whatever I do. For example, I want to list _all_dbs. Making that call with basic authentication works. making it from curl works with cookies. Just from the browser it just won't. I have asked Jan on the couchDB slack channel and he suggests having the site on the same domain to not have to deal with the pest of CORS, but offered no solution to having it cross domains. It should be possible, I understand slouch could do this, and pouchDB can. so there is some trick that eludes me.

Any help at all would be very appreciated. Sorry for using an issue to communicate to you, I did not find any other contact channel!

cheers, Jon

Support for CouchDB 3.0's partitioned database

Any plan for adding support for CouchDB 3.0? In particular partitioned database?

Support for binary upload of attachments

Slouch currently supports adding attachments via a base64 encoded value in the _attachments attribute of a doc. Use the work commented out at https://github.com/redgeoff/slouch/blob/master/scripts/attachment.js#L10 to enable a method of uploading attachments that are binary data.

In my testing, it appears that the binary upload is either broken at the request/browserify layer or is not in the format expected by CouchDB. If the issue is at the request layer then we may want to use something like needlejs for just these binary uploads.

Add URL (minus password) to error messages

CouchDB spits out errors like "Database does not exist" without the name of a DB. This isn't very useful when there are a lot of requests or Slouch is being used from a high level. Let's modify https://github.com/redgeoff/slouch/blob/master/scripts/enhanced-request.js#L55 to insert the URL into the error. The code at https://github.com/redgeoff/spiegel/blob/master/src/utils.js#L28 can be used to censor the password--it may even be a good idea to place this censorPassword() function in the sporks layer.

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

Version 3.5.2 of bluebird was just published.

Branch	Build failing 🚨
Dependency	bluebird
Current Version	3.5.1
Type	dependency

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

bluebird 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: Your tests failed on CircleCI (Details).

Release Notes

v3.5.2

Bugfixes:

Fix PromiseRejectionEvent to contain .reason and .promise properties. (#1509, #1464)
Fix promise chain retaining memory until the entire chain is resolved (#1544, #1529)

id: changelog
title: Changelog

Commits

The new version differs by 22 commits.

50067ec Release v3.5.2
f290da0 Fix memory being retained until promise queue is completely empty (#1544)
ad6d763 Update benchmarks (#1539)
49da1ac Fix a typo. (#1534)
b06106a Fix typo in readme introduced in #1530 (#1531)
c1dc5b9 Update README.md (#1530)
e35455f chore: clone last 5 commits (#1521)
91ae9ce chore: add Node.js 10 (#1523)
9159472 Added a simple usage example (#1369)
39081ba Update promise.each.md (#1479)
77781fe Fix header (#1513)
b8eedc1 Update LICENSE to 2018 (#1490)
4163e82 Added ES6 way to import the bluebird promise (#1461)
3790a92 DOC: add direct link to Promise.delay from API ref (#1465)
e8d8525 Update error documentation (#1469)

There are 22 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 sporks is breaking the build 🚨

The dependency sporks was updated from `1.0.0` to `1.0.1`.

🚨 View failing branch.

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

sporks 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: Your tests failed on CircleCI (Details).

Commits

The new version differs by 26 commits.

9bb6218 chore(version): 1.0.1
6f91ec3 Merge pull request #31 from redgeoff/greenkeeper/gofur-1.1.1
0bf1f51 chore(packages): update
e3fd9d0 chore(package): update gofur to version 1.1.1
d305b73 Merge pull request #29 from redgeoff/redgeoff-patch-1
496ba5d test(circleci): latest node
f1282a0 Merge pull request #28 from redgeoff/greenkeeper/events-3.0.0
a3f8cd9 fix(package): update events to version 3.0.0
1f894d1 Merge pull request #27 from redgeoff/greenkeeper/request-2.87.0
fdc0741 chore(package): update request to version 2.87.0
59a4e2d Update gofur to the latest version 🚀 (#25)
07fec8a Circleci 2.0 (#24)
38c3e43 Merge pull request #22 from redgeoff/greenkeeper/gofur-1.0.2
80e4767 chore(package): update gofur to version 1.0.2
245f2d4 Merge pull request #21 from redgeoff/greenkeeper/events-2.0.0

There are 26 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 🌴

How do I do cookie authentication?

I am trying to implement one-database-per-user with a service on my express app using slouch, it looks like that:

const Slouch = require('couch-slouch')
const config = require('./config')

const slouch = new Slouch(config.couchDb.url)

module.exports = {
  createDb(user) {
    const dbName = `${config.couchDbBaseName}_${user.email}`
    return slouch.user.createSession({
      username: config.couchDb.username,
      password: config.couchDb.password
    })
    .then(response => slouch.user.create(user.email, user.dbpwd))
    .then(response => slouch.db.create(dbName))
    .then(response => slouch.security.set(dbName, {
        admins: { names: [], roles: [] },
        members: { names: [user.email], roles: [] }
      })
    )
  }
}

I was hoping some magic would happen and the cookie from the createSession response would be sent with the next commands. But although the user creation works (maybe my db lets anyone create users? oops), the following slouch.db.create call is failing with 'unauthorized'. If there a way to get through this?

Fix cookie authentication in the browser

As per

slouch/test/spec/user.js

Line 134 in da7ca11

    
           // TODO: get authenticate() and authenticated() working properly in the browser. For now, we

authenticate() and authenticated() are not working properly in the browser. For now, we have to fake the responses as it appears that the session cookie is not being propagated from the session post to the session get.

Set the dbname once

It's a pain to have to specify the database name every function call. Is there a way to configure this during instantiation so that you don't have to type it every time?

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

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

Version 2.84.0 of request was just published.

Branch	Build failing 🚨
Dependency	request
Current Version	2.83.0
Type	dependency

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

request 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 Your tests failed on CircleCI Details

Commits

The new version differs by 6 commits.

d77c839 Update changelog
4b46a13 2.84.0
0b807c6 Merge pull request #2793 from dvishniakov/2792-oauth_body_hash
cfd2307 Update hawk to 7.0.7 (#2880)
efeaf00 Fixed calculation of oauth_body_hash, issue #2792
253c5e5 2.83.1

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

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

Version 1.0.2 of gofur was just published.

Branch	Build failing 🚨
Dependency	gofur
Current Version	1.0.1
Type	devDependency

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

gofur 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 A command timed out during your tests Details

Release Notes

v1.0.2

#27 - chore(packages): update

Commits

The new version differs by 11 commits.

d091394 chore(version): 1.0.2
da80fd8 Merge pull request #27 from redgeoff/mocha
0a9bdfa chore(packages): update
b385e78 chore(mocha): 5.0.2
aeb4571 Merge pull request #26 from redgeoff/greenkeeper/browserify-16.0.0
b57a161 fix(package): update browserify to version 16.0.0
a293f4d Merge pull request #25 from redgeoff/greenkeeper/mocha-5.0.0
4caaa70 fix(package): update mocha to version 5.0.0
2ab2939 Merge pull request #24 from redgeoff/greenkeeper/browserify-15.0.0
c673af6 fix(package): update browserify to version 15.0.0
ad67d4a doc(readme): debug browser test

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

The devDependency wait-on was updated from `4.0.0` to `4.0.1`.

🚨 View failing branch.

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

Status Details

❌ ci/circleci: Your tests failed on CircleCI (Details).

Commits

The new version differs by 6 commits.

af9de4e 4.0.1
00d2828 Merge branch 'markhoney-patch-1'
3649437 Merge branch 'patch-1' of https://github.com/markhoney/wait-on into markhoney-patch-1
6e4449f Merge branch 'stephengcox-vuln/joi'
8104278 update hapi/joi for SRCCLR-SID-22483 vulnerability
d9d23aa Fix typos

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 🚨

The devDependency mocha was updated from `6.1.0` to `6.1.1`.

🚨 View failing branch.

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

Status Details

❌ ci/circleci: Your tests failed on CircleCI (Details).

Release Notes for v6.1.1

6.1.1 / 2019-04-07

🐛 Fixes

Fix Windows End-of-Line publishing issue

Commits

The new version differs by 3 commits.

9b516bf Release v6.1.1
9e138b1 update CHANGELOG for v6.1.1 [ci skip]
d7de948 Set eol for publishing

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 🌴

Set cookie whenever request has Set-Cookie header

As per https://stackoverflow.com/a/10359837/2831606, if we are not using persistent cookies (allow_persistent_cookies=false) then CouchDB can change/refresh our cookie during any request. If this happens, we should update the locally stored cookie. The code to set the cookie would look something like this

Create changesArray

slouch/scripts/db.js

Line 110 in 53e184c

DB.prototype.viewArray = function (dbName, viewDocId, view, params) {

but for the _changes endpoint

Latest release (1.0.5) on npm does not include doc.find implementation

Although it exist here on github, on npm it doesn't seem to have the latest updates.
https://www.npmjs.com/package/couch-slouch

Have to add quotes and escape them for startkey/endkey to work

        database.doc.all "dbname", {
          startkey: "\"alpha\"",
          endkey: "\"bravo\ufff0\"",
          include_docs: true
        }
        .each (row) => ...

Is this by design? This isn't the case for PouchDB. The extra escaped quotes are ugly.

(sorry for the coffeescript!)

Generator support

Option to use generators to iterate through stream iterators. Probably need to wait for async iterators: https://github.com/tc39/proposal-async-iteration

db.create() should not succeed if the db already exists

Comment out the following until we document exactly what error is thrown?

https://github.com/redgeoff/slouch/blob/master/scripts/db.js#L23

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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Complete documentation for API reference

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

The dependency bluebird was updated from `3.5.3` to `3.5.4`.

🚨 View failing branch.

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

bluebird 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: Your tests failed on CircleCI (Details).

Release Notes for v3.5.4

Proper version check supporting VSCode(#1576)

Commits

The new version differs by 6 commits.

e0222e3 Release v3.5.4
4b9fa33 missing --expose-gc flag (#1586)
63b15da docs: improve and compare Promise.each and Promise.mapSeries (#1565)
9dcefe2 .md syntax fix for coming-from-other-languages.md (#1584)
b97c0d2 added proper version check supporting VSCode (#1576)
499cf8e Update jsdelivr url in docs (#1571)

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 🌴

Remove `request` from Slouch

Can we get request removed as it is unmaintained has known security vulnerabilities.

PVR0429040/PVR0429046 for CVE-2023-28155 in request

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

The devDependency gofur was updated from `1.1.0` to `1.1.1`.

🚨 View failing branch.

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

Status Details

❌ ci/circleci: Your tests failed on CircleCI (Details).

Commits

The new version differs by 13 commits.

cbfd5cb chore(version): 1.1.1
4237151 Merge pull request #45 from redgeoff/update-packages
079ac71 chore(packages): update
6e3184d Merge pull request #44 from redgeoff/redgeoff-patch-1
5025bce test(circleci): latest node
36e4e3c Merge pull request #43 from redgeoff/greenkeeper/fs-extra-7.0.0
0dffe09 fix(package): update fs-extra to version 7.0.0
5635bba feat(packages): update mocha-headless-chrome and selenium-standalone (#42)
5d5e680 Merge pull request #41 from redgeoff/chrome
421be5f test(headless): now need to install chrome
103379b Merge pull request #38 from redgeoff/greenkeeper/fs-extra-6.0.0
caf001b fix(package): update fs-extra to version 6.0.0
5b9ca73 fix(browser-coverage): restore grep (#36)

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 🌴

Passing in a large number of doc ids to all fails

Problem is that all is using GET when it should use a POST. I've tried to fix it, but it's not right. If I figure it out I can send a pull request.

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

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

Version 1.0.3 of gofur was just published.

Branch	Build failing 🚨
Dependency	gofur
Current Version	1.0.2
Type	devDependency

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

Status Details

❌ ci/circleci Your tests failed on CircleCI Details

Release Notes

v1.0.3

#32 - test(circleci): migrate to 2.0
#31 - #31

Commits

The new version differs by 4 commits.

a446d0d chore(version): 1.0.3
798fb63 test(circleci): migrate to 2.0 (#32)
3c57dcf feat(test): headless testing with chrome (#31)
3b2435f doc(readme): phantomjs locally

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 🌴

Support for /db/_find

Right now, slouch doesn't seem to provide support for document retrieval using the POST /{db}/_find endpoint in the CouchDB API (see https://docs.couchdb.org/en/latest/api/database/find.html) or something similar.

It would be good if the ability to find documents based on some queries instead of just the ID could be added.

Get CircleCI tests working with CouchDB 1

As per https://github.com/redgeoff/slouch/blob/master/circle.yml#L50: replication and a number of other things doen't appear to be working with the official couchdb 1.6.1 docker image. We'll probably need to build a custom image for these tests.

First 8 charcters of view id is escaped

Why are we leaving first 8 characters of view id when calling a couchdb view in here?

slouch/scripts/db.js

Line 120 in 239272a

var encodedViewDocId = '_design/' + encodeURIComponent(viewDocId.substr(8));

Tests are now failing in master

Something appears to have broken in the npm run browser-test flow even though there have been no changes to the Slouch code or its dependencies.

See https://app.circleci.com/pipelines/github/redgeoff/slouch/65/workflows/b0d731d2-0da8-4046-bc5b-91bd84962f9c/jobs/461

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

Version 2.87.0 of request was just published.

Branch	Build failing 🚨
Dependency	`request`
Current Version	2.86.0
Type	dependency

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

request 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 Your tests failed on CircleCI Details

Commits

The new version differs by 4 commits.

02fc5b1 Update changelog
de1ed5a 2.87.0
a6741d4 Replace hawk dependency with a local implemenation (#2943)
a7f0a36 2.86.1

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 🌴

Missing log statement for error

At https://github.com/redgeoff/slouch/blob/master/scripts/enhanced-request.js?utf8=%E2%9C%93#L128

redgeoff / slouch Goto Github PK

slouch's Introduction

slouch

Slouch is a good alternative to nano:

Table of Contents

slouch's People

Contributors

Stargazers

Watchers

Forkers

slouch's Issues

The devDependency wait-on was updated from 3.1.0 to 3.2.0.

Version 4.1.2 of chai just got published.

Bug Fixes

Docs

Version 5.0.2 of mocha was just published.

5.0.2 / 2018-03-05

🐛 Fixes

:nut_and_bolt Other

Version 5.0.1 of mocha was just published.

Version 3.5.2 of bluebird was just published.

id: changelog title: Changelog

The dependency sporks was updated from 1.0.0 to 1.0.1.

Version 2.84.0 of request was just published.

Version 1.0.2 of gofur was just published.

The devDependency wait-on was updated from 4.0.0 to 4.0.1.

The devDependency mocha was updated from 6.1.0 to 6.1.1.

6.1.1 / 2019-04-07

🐛 Fixes

The dependency bluebird was updated from 3.5.3 to 3.5.4.

The devDependency gofur was updated from 1.1.0 to 1.1.1.

Version 1.0.3 of gofur was just published.

Version 2.87.0 of request was just published.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency wait-on was updated from `3.1.0` to `3.2.0`.

id: changelog
title: Changelog

The dependency sporks was updated from `1.0.0` to `1.0.1`.

The devDependency wait-on was updated from `4.0.0` to `4.0.1`.

The devDependency mocha was updated from `6.1.0` to `6.1.1`.

The dependency bluebird was updated from `3.5.3` to `3.5.4`.

The devDependency gofur was updated from `1.1.0` to `1.1.1`.