The node-packages from favware

Depfu Error: No dependency files found

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

Go to the Settings page of either your own account or the organization you've used
Go to "Installed Integrations"
Click the "Configure" button on the Depfu integration
Remove this repo (favware/node-packages) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

[Request]: Export other YTDL-core functions

Is your feature request related to a problem? Please describe.
For my music bot on Discord, I'd like to have information about the song as well as the player itself

Describe the ideal solution
Exporting ytdl-core functions alongside the custom play one

Describe alternatives you've considered
Use both ytdl-core and ytdl-prismedia

Further details:

Affected package(s): ytdl-prismedia
Version of the package: Latest
Priority this request should have – please be realistic and elaborate if possible:
- Low
- Medium
- High
- Severe

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

The devDependency rollup-plugin-commonjs was updated from `10.0.2` to `10.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-commonjs 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: lockfile_update: Your tests failed on CircleCI (Details).
❌ node-multi-build: * lockfile_update - Failed

node-v10 - Blocked
node-v11 - Blocked
node-v12 - Blocked
lockfile_upload - Blocked

Commits

The new version differs by 4 commits.

12a11c2 10.1.0
82ca3a2 Update changelog
fcd9826 Normalize ids before looking up in named export map (#406)
e431c29 Update README.md with note on symlinks (#405)

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 🌴

Depfu Error: No dependency files found

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

Go to the Settings page of either your own account or the organization you've used
Go to "Installed Integrations"
Click the "Configure" button on the Depfu integration
Remove this repo (favware/node-packages) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

Depfu Error: No dependency files found

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

Go to the Settings page of either your own account or the organization you've used
Go to "Installed Integrations"
Click the "Configure" button on the Depfu integration
Remove this repo (favware/node-packages) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

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

The devDependency lint-staged was updated from `9.2.4` to `9.2.5`.

🚨 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: lockfile_update: Your tests failed on CircleCI (Details).
❌ node-multi-build: * lockfile_update - Failed

node-v11 - Blocked
node-v10 - Blocked
node-v12 - Blocked
lockfile_upload - Blocked

Release Notes for v9.2.5

9.2.5 (2019-08-27)

Bug Fixes

validateConfig validates function task return values (d8fad78)

Commits

The new version differs by 1 commits.

d8fad78 fix: validateConfig validates function task return values

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 🌴

Depfu Error: No dependency files found

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

Go to the Settings page of either your own account or the organization you've used
Go to "Installed Integrations"
Click the "Configure" button on the Depfu integration
Remove this repo (favware/node-packages) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

dummy issue to trigger label sync

Depfu Error: No dependency files found

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

Go to the Settings page of either your own account or the organization you've used
Go to "Installed Integrations"
Click the "Configure" button on the Depfu integration
Remove this repo (favware/node-packages) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

Depfu Error: No dependency files found

Hello,

We've tried to activate or update your repository on Depfu and couldn't find any supported dependency files. If we were to guess, we would say that this is not actually a project Depfu supports and has probably been activated by error.

Monorepos

Please note that Depfu currently only searches for your dependency files in the root folder. We do support monorepos and non-root files, but don't auto-detect them. If that's the case with this repo, please send us a quick email with the folder you want Depfu to work on and we'll set it up right away!

How to deactivate the project

Go to the Settings page of either your own account or the organization you've used
Go to "Installed Integrations"
Click the "Configure" button on the Depfu integration
Remove this repo (favware/node-packages) from the list of accessible repos.

Please note that using the "All Repositories" setting doesn't make a lot of sense with Depfu.

If you think that this is a mistake

Please let us know by sending an email to [email protected].

This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.

Dependency Dashboard

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

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

chore(deps): update all non-major dependencies (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, turbo, vite)

Detected dependencies

npm

package.json

@commitlint/cli ^18.4.3

@commitlint/config-conventional ^18.4.3

@lerna-lite/cli ^3.1.0

@sapphire/eslint-config ^5.0.3

@sapphire/prettier-config ^2.0.0

@sapphire/ts-config ^5.0.0

@types/node ^20.10.4

@typescript-eslint/eslint-plugin ^6.13.2

@typescript-eslint/parser ^6.13.2

@vitest/coverage-v8 ^1.0.4

cz-conventional-changelog ^3.3.0

eslint ^8.55.0

eslint-config-prettier ^9.1.0

eslint-plugin-prettier ^5.0.1

lint-staged ^15.2.0

npm-run-all ^4.1.5

prettier ^3.1.1

rimraf ^5.0.5

turbo ^1.11.1

typescript ^5.3.3

vite ^5.0.7

vitest ^1.0.4

ansi-regex ^5.0.1

minimist ^1.2.8

yarn 4.0.2

packages/converter/package.json

tsup ^8.0.1

packages/crypto/package.json

tsup ^8.0.1

packages/querystring/package.json

tsup ^8.0.1

packages/yamlreader/package.json

js-yaml ^4.1.0

@types/js-yaml ^4.0.9

tsup ^8.0.1

@types/js-yaml ^4.0.9

packages/zalgo/package.json

tsup ^8.0.1

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

favware / node-packages Goto Github PK

node-packages's People

Contributors

Stargazers

Watchers

node-packages's Issues

Monorepos

How to deactivate the project

If you think that this is a mistake

The devDependency rollup-plugin-commonjs was updated from 10.0.2 to 10.1.0.

Monorepos

How to deactivate the project

If you think that this is a mistake

Monorepos

How to deactivate the project

If you think that this is a mistake

The devDependency lint-staged was updated from 9.2.4 to 9.2.5.

9.2.5 (2019-08-27)

Bug Fixes

Monorepos

How to deactivate the project

If you think that this is a mistake

Monorepos

How to deactivate the project

If you think that this is a mistake

Monorepos

How to deactivate the project

If you think that this is a mistake

Awaiting Schedule

Detected dependencies

Recommend Projects

Recommend Topics

Recommend Org

The devDependency rollup-plugin-commonjs was updated from `10.0.2` to `10.1.0`.

The devDependency lint-staged was updated from `9.2.4` to `9.2.5`.