goto-bus-stop/plug-auth

Browser and Node.js libraries for third-party authentication with plug.dj

plug-auth

JavaScript libraries for third-party authentication with plug.dj.

On the client

plug-auth-client

On the server

plug-auth-server

How it works

plug-auth works by verifying that a user has access to the account they claim to be.

1. plug-auth gives the user a unique token
2. the user changes their profile blurb (bio) to include the token value
3. plug-auth checks that the user's blurb includes the token value
4. plug-auth grants access and generates a JSON Web Token that can be used to verify the user's identity again later
5. the user changes their blurb back

Building

The client and server packages are both maintained in a single repo (this one). You can build them both by:

npm run build

Testing

plug-auth uses ava for tests and standard for linting.

To run tests:

npm run ava

To lint:

npm run lint

To do both:

npm test

License

MIT

plug-auth's Issues

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

The devDependency rollup was updated from 1.18.0 to 1.19.0.

🚨 View failing branch.

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 6 commits.

• 9af119d 1.19.0
• b3f361c Update changelog
• 456f4d2 Avoid variable from empty module name be empty (#3026)
• 17eaa43 Use id of last module in chunk as name base for auto-generated chunks (#3025)
• 871bfa0 Switch to a code-splitting build and update dependencies (#3020)
• 2443783 Unified file emission api (#2999)

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 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

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

The devDependency rollup-plugin-babel was updated from 4.0.3 to 4.1.0.

🚨 View failing branch.

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

rollup-plugin-babel 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 12 commits.

• de25402 4.1.0
• 4f09a91 4.1.0-1
• bb58960 Return null from the transform hook when it doesn't transform anything
• 97953e1 Fix indentation in examples of configuration in readme (#266)
• becd7ea Remove babel 6 test from AppVeyor (#263)
• 5168424 Upgraded husky
• 3a9ba87 Add options.extensions to README (#256)
• b709cad 4.1.0-0
• 8dbe1d2 Tweak eslint rules to stop conflicting with prettier output
• 01d2095 Run prettier over the repo files
• 6bb0e49 Setup prettier
• 22f1b81 Fix preflightChecks for ignored files

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

Version 3.2.2 of cross-env just got published.

Branch	Build failing 🚨
Dependency	cross-env
Current Version	3.2.1
Type	devDependency

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

As cross-env 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.2.2

<a name"3.2.2">

3.2.2 (2017-03-04)

Bug Fixes

• bin require (b303b9f5)

Commits

The new version differs by 2 commits .

• b303b9f fix: bin require
• 85b8e8a docs: contributor member (#66)

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 🚨

The devDependency rollup was updated from 1.9.2 to 1.9.3.

🚨 View failing branch.

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

---

Release Notes for v1.9.3

2019-04-10

Bug Fixes

• Simplify return expressions that are evaluated before the surrounding function is bound (#2803)

Pull Requests

• #2803: Handle out-of-order binding of identifiers to improve tree-shaking (@lukastaegert)

Commits

The new version differs by 3 commits.

• 516a06d 1.9.3
• a5526ea Update changelog
• c3d73ff Handle out-of-order binding of identifiers to improve tree-shaking (#2803)

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 🚨

The devDependency rollup was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

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

---

Release Notes for v1.14.3

2019-06-06

Bug Fixes

• Generate correct external imports when importing from a directory that would be above the root of the current working directory (#2902)

Pull Requests

• #2902: Use browser relative path algorithm for chunks (@lukastaegert)

Commits

The new version differs by 4 commits.

• c68bd95 1.14.3
• d79aa57 Update changelog
• 7179390 Use browser relative path algorithm for chunks (#2902)
• b1df517 Add funding button

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

Version 3.2.0 of cross-env just got published.

Branch	Build failing 🚨
Dependency	cross-env
Current Version	3.1.4
Type	devDependency

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

As cross-env 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 could not complete due to an error Details

Release Notes

v3.2.0

<a name"3.2.0">

3.2.0 (2017-03-04)

Features

• revamp: revamp the entire lib (backward compatible) (#63) (dad00c46)

Commits

The new version differs by 4 commits .

• dad00c4 feat(revamp): revamp the entire lib (backward compatible) (#63)
• e33a85c docs(README): Add doc for cross-var. (#58)
• 5e590ec docs(README): added how to use cross-env to run npm sub-scripts (#53)
• afdb2de docs(README): mention Bash on Windows (#49)

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

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.1.1 to 7.1.2.

• The devDependency @babel/preset-env was updated from 7.0.0 to 7.1.0.
• The devDependency @babel/register was updated from 7.0.0-rc.4 to 7.0.0.

🚨 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 babel7 group definition.

babel7 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).

---

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 🌴

[client] authenticate method never resolves.

using the following code with what is essentially the example server app yields no results

authenticate({
    transport: httpTransport({ url: 'https://my-url/auth/login' })
}).then((result) => {
    console.log(result);
    if (!result || !result.token) console.log('no result or token');
}).catch(console.error);

This only seems to be an issue with version 1.1.1, using 1.1.0 works as intended. I wasn't able to find the source of the issue, sorry :(

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.

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

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

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

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

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

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

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

Commits

The new version differs by 3 commits .

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

See the full diff.

Not sure how things should work exactly?

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

---

Your Greenkeeper Bot 🌴