I’d like oauth-login-url to be compatible with https://www.pikapkg.com/.

I’d also like to try adding the module build to the published npm package and then let modern browsers import the module directly from CDN services such as https://unpkg.com/ (set "unpkg" field in package.json)

Please mark the @octokit/oauth-login-url package as deprecated on NPM. I was using it and only found out that it was deprecated by coming to this repository.

The devDependency semantic-release was updated from 17.0.0 to 17.0.1.

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

Your Greenkeeper Bot 🌴

The GitHub documentation says that the scope parameter for an OAuth app is scope, not scopes:

https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#1-request-a-users-github-identity

This library generates URLs with &scopes=xyz though, when it really should be &scope=xyz.

It seems as though that version was never published, and since v1.0.0 contains no files at all, the package is unusable

Description

Node v10 has been deprecated so there is no need to keep giving support to it in our CI.

Context

You can find more details here

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

• 🙋 Claim this issue: Comment below.

  More than one person can work on this issue, don't worry if it's already claimed.

• 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

@@ -17,11 +17,11 @@ See [GitHub’s Developer Guide for the OAuth web application flow](https://deve
       </th>
       <td width=100%>
   
-Load `@octokit/oauth-authorization-url` directly from [cdn.pika.dev](https://cdn.pika.dev)
+Load `@octokit/oauth-authorization-url` directly from [cdn.skypack.dev](https://cdn.skypack.dev)
 
 ```html
 <script type="module">
-  import { oauthAuthorizationUrl } from "https://cdn.pika.dev/@octokit/oauth-authorization-url";
+  import { oauthAuthorizationUrl } from "https://cdn.skypack.dev/@octokit/oauth-authorization-url";
 </script>
 ```
 

• 💾 Commit your changes

• 🔀 Start a Pull Request. There are two ways how you can start a pull request:

  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
  2. You can edit files directly in your browser

• 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

The devDependency semantic-release was updated from 17.0.1 to 17.0.2.

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

Your Greenkeeper Bot 🌴

This issue contains a list of Renovate updates and their statuses.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to ignore the schedule.

• fix(deps): lock file maintenance

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

The devDependency ts-jest was updated from 25.1.0 to 25.2.0.

🚨 View failing branch.

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

ts-jest 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.

Your Greenkeeper Bot 🌴

to match the terminology of the OAuth 2 specification

The devDependency @types/jest was updated from 25.1.1 to 25.1.2.

🚨 View failing branch.

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

@types/jest 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.

Your Greenkeeper Bot 🌴

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.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'packageRules[1].npm' should be a json object, Invalid configuration option: @pika/pack, Invalid configuration option: author, Invalid configuration option: files, Invalid configuration option: jest, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: name, Invalid configuration option: packageRules[0].@pika/pack, Invalid configuration option: packageRules[0].@pika/plugin-build-node, Invalid configuration option: packageRules[0].@pika/plugin-build-web, Invalid configuration option: packageRules[0].@pika/plugin-ts-standard-pkg, Invalid configuration option: packageRules[0].@types/jest, Invalid configuration option: packageRules[0].jest, Invalid configuration option: packageRules[0].pika-plugin-unpkg-field, Invalid configuration option: packageRules[0].semantic-release, Invalid configuration option: packageRules[0].ts-jest, Invalid configuration option: packageRules[0].typescript, Invalid configuration option: packageRules[1].i, Invalid configuration option: publishConfig, Invalid configuration option: release, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version, The "npm" object can only be configured at the top level of a config but was found inside "packageRules[1]"

The devDependency @types/jest was updated from 25.1.0 to 25.1.1.

🚨 View failing branch.

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

@types/jest 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.

Your Greenkeeper Bot 🌴

Follow up to #186

Ideally we would do a test_matrix step and then a test step that depends on test_matrix, so that for branch protections we can require test independent of the Node versions we are using.

See this for reference: https://github.com/octokit/core.js/blob/393caf31b2e802ea9be59aa84f90d64f98953fdb/.github/workflows/test.yml#L32