crates is an extension aims to help people to manage their dependencies for rust (crates.io & TOML).

Seray Uzgur

Last update: Jan 4, 2023

Related tags

IDEs rust toml crates cargo vscode-extension dependencies

Overview

crates

Hello Rust & VSCode lovers,

This is crates, an extension for crates.io dependencies. Aims helping developers to manage dependencies while using Cargo.toml.

Notes

It is only helpful if you are using dependencies from crates.io. Dependencies from git or other platforms are not supported.
TOML must be valid. If not, crates will not show versions. It will inform you with the status bar and dialog.

Features

crates is very simple. It has just two features.

Displays the latest version of the crate next to it
Shows all versions (clickable) on the tooltip of the crate hovered.

Aims to be fast and simple.

Update Single Dependency

Update All Dependencies (lazy mode)

Simple settings

It is so simple that you do not need any configuration, but if you insist...

crates.useLocalCargoIndex: If true, crates will use local cargo repository.

crates.localCargoIndexHash: he hash path for crates.io index. Default value goes to official index. Alternative values would support registry source mirror with source replacement setup.

crates.githubAuthBasic: The <username>:<personal-access-token> or <username>:<password> for accessing Github API with increased access rates 5000 req/h.

crates.errorDecorator: The text to show when a dependency has errors. Default is ❗️ ❗️ ❗️ .

crates.compatibleDecorator: The text template to show when a dependency is semver compatible. ${version} will be replaced by the latest version info. Default is ' ✅ '

crates.incompatibleDecorator: The text template to show when a dependency is not semver compatible. ${version} will be replaced by the latest version info. Default is ' ❌ ${version}'

crates.listPreReleases: If true, pre-release versions will be listed in hover and at decoration. The default is false.

Known Issues

All glitches will be cleared on save.

Thanks to

@ademozay

@userzimmermann

@RensAlthuis

oli-obk (First Patron)

Comments

Goto Docs

It would be very helpful to have Goto Docs in the Crates Extension. It should open the link https://docs.rs/ cratename example: the latest version https://docs.rs/wasm-bindgen-futures or the exact version https://docs.rs/wasm-bindgen-futures/0.4.8 Image of the feature:
enhancement

opened by bestia-dev 15
Can't Change Version Twice in a Row Until First Saving the TOML File.
Describe the bug When I hover over the version of a crate, I see the list of possible versions to choose from as expected. Then I accidentally choose a version I didn't mean to choose. When hovering over the incorrect version, I still get the list as expected, but now I cannot select the correct version I originally meant to select. The only way I can select the correct version is if I save the file first.

Expected behavior To be able to change the version as many times as I want without needing to save the .toml file between each selection.

Desktop (please complete the following information):

OS: Windows 10

Version 0.3.4

help wanted
opened by ozyman42 15
Incorrectly marking 1.4.0 as incompatible with 1.3

Cargo ignores leading zero components of the version number when considering compatibility. So while 0.1.0 and 0.2.0 are not compatible, 1.3.0 and 1.4.0 are (as are 2.2.0 and 2.5.0). Also as far as I know 0.0.1 and 0.0.2 are also incompatible.

opened by djc 13
Show different status indicator for semver-compatible updates

First let me say that I just recently discovered your extension on Twitter and I love it. That said, I think it could be better still, so here's one little suggestion.

Is your feature request related to a problem? Please describe. When reviewing dependency versions I'm usually hunting for semver-incompatible updates, since I use cargo update to bump all the semver-compatible ones. I noticed that your extension already shows 👍 for versions that are set to "1" for example, but actually it could/should also do this for crates that are set to "1.0.1" for example, since these are semver-compatible cargo will pull in the updates automatically. Setting it to 1.0.1 might be common if you've never tested your crate with 1.0.0 for example, or if you know you need a bugfix from 1.0.1. (Just in case you're not aware, in Cargo.toml "1.0.0" is equivalent to "^1.0.0" rather than "=1.0.0" -- you probably always want to be show semver-compatible updates in the latter case.)

Describe the solution you'd like Right now your extension either shows 👍 or "Latest: 1.2.3" by default. However, it seems to show "Latest: 1.2.3" even if I have say "1.1.2" configured. It would be nice if it could distinguish between semver-incompatible updates (as in, "2.0") and semver-compatible updates ("1.2.3"). The simplest way to do this could be to show 👍 for semver-compatible updates. A slightly more advanced way could be to distinguish between the case of semver-compatible and the case of semver-incompatible updates (for example, 👍 1.2.3 for semver-compatible and "Latest: 1.2.3" for -incompatible).
enhancement

opened by djc 13
Error: The requested blob is too large to fetch via the API

I use Crates 0.4.7. VSCode Extension on windows with Remote -WSL. The code is actually inside Windows Subsystem for Linux (Debian 10 backend) and only the frontend is in windows. In my cargo.toml the Crates Extension draws a red exclamation sign near web.sys like this:

[dependencies.web-sys] version = "0.3.27" ! features = [ "AbortController", "console", ....

The error msg is: web-sys: StatusCodeError: 403 - "{"message":"This API returns blobs up to 1 MB in size. The requested blob is too large to fetch via the API, but you can use the Git Data API to request blobs up to 100 MB in size.", "errors":[{"resource":"Blob","field":"data","code":"too_large"}], "documentation_url":"https://developer.github.com/v3/repos/contents/#get-contents"}"

Is it possible to correct this error?

Thanks
enhancement

opened by bestia-dev 13
Win 10 path missing a slash
Describe the bug ~Local cargo index git path~ The error message is missing some backslashes.

To Reproduce When I have useLocalCargoIndex set to true, I get this error:

**clap: Error: Command failed: git --no-pager --git-dir="C:\Users\Samz.cargo\registry\index\github.com-1ecc6299db9ec823.git" show origin/master:cl/ap/clap fatal: invalid object name 'origin/master'. ** ( Check Reviews )

Expected behavior The user dir is faultly Samz.cargo and should be Samz\.cargo, and github.com-1ecc6299db9ec823.git should have \.git

Desktop (please complete the following information):

OS: Windows

Version: 10.0.19042

Additional context Seems to be the case in 0.5.6 and 0.5.7 (not sure why it worked until 0.5.7 update tho) Perhaps related to this #116 ?

EDIT: Corrected some details about the issue, also see my comment
bug help wanted
opened by Samzyre 12
Accessibility regression
Describe the bug The previous version used symbols to indicate status; the current version uses only color. I'm colorblind (as are about 10% of males). This is not useful to me.

To Reproduce Steps to reproduce the behavior:

Open your Cargo.toml file containing one or more dependencies.

Expected behavior I expect symbols to make it easy to tell the status of my dependencies.

Screenshots

Desktop (please complete the following information):

OS: macOS 10.15.5

Version: vscode 1.48.2; crates 0.5.3
opened by dcormier 9
Local Cargo Index doesn't work when user home directory path has a space
Describe the bug The git command executed by the extension fails (at least on Win10) if there is a space in the user's home directory. It can probably be fixed by surrounding the directory with quotes.

The space in the name causes part of the path to be interpreted as a git subcommand.

To Reproduce Steps to reproduce the behavior:

Create a user with a space in their username on Windows

Install VS Code w/ the Crates extension

Enable the Use Local Cargo Index feature

Open Cargo.toml, all dependencies will have ! next to them. Hovering over it to see the error reveals the issue.

Expected behavior Local index should work even if the user has spaces in their username

Screenshots

Desktop (please complete the following information):

OS: Win10

bug
opened by dljsjr 8
Move from GitHub v3 API to v4 to reduce risk of too many queries
I'm seeing that we're still hitting the rate limit for nushell (https://github.com/nushell/nushell).

Something I've noticed using both v3 and v4 APIs for GitHub is that with v3 it's pretty easy, even with authentication, to hit your rate limit. Since you can only send one query at a time, you end up naturally hitting it unless you add artificial delays in the queries.

At one point working with the GitHub API to track language popularity, I moved my tool over to the v4 APIs. Here's an example of the kind of query string I'd use:

{"query": "query { lang0: search(type:ISSUE, query: \"language:JavaScript type:pr created:2019-11-04..2019-11-11\") { issueCount } lang1: search(type:ISSUE, query: \"language:Java type:pr created:2019-11-04..2019-11-11\") { issueCount } }"}

Which is this bit of GraphQL:

query { lang0: search(type:ISSUE, query: "language:JavaScript type:pr created:2019-11-04..2019-11-11") { issueCount } lang1: search(type:ISSUE, query: "language:Java type:pr created:2019-11-04..2019-11-11") { issueCount } }

When that's run, each answer gets a label attached to it that can be queried back out. This lets you run a bunch of queries all at once and it's generally much easier to stay in your rate limit this way (v4 rate limits work differently than v3).
opened by jntrnr 7
Plugin sends too many concurrent requests to crates.io

We're periodically seeing abnormal spikes in traffic that originate from this plugin. It appears to send a request for every crate it wants to know about concurrently, with no limiting of any kind in place. We're frequently seeing upwards of 50+ concurrent requests from the same IP identifying as this plugin.

This is in violation of the crates.io crawler policy. At minimum these requests need to be sent serially rather than in parallel.

Thank you for setting a proper user-agent header so I am able to reach out without having to resort to blocking traffic

opened by sgrif 7
workspace references with paths are problematic
Describe the bug A clear and concise description of what the bug is.

I've recently split up a cargo project into workspaces with a cli package refering to a lib package by path. When I remove the reference by path the crates ext is successful. When added back I get a stream of error dialogs about it failing and screen of flickering thumbs!

To Reproduce Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

Setup a cargo workspace project with at least two package and at least one package referencing another by path

See error

Expected behavior A clear and concise description of what you expected to happen.

Crates extension understands that the dependency exists locally retry with error dialogs.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS] osx

Version [e.g. 22] 0.3.2 (latest at this time )

Additional context Add any other context about the problem here.

trying to split up a mono cargo package into separate lib and cli packages with a workspace
bug
opened by softprops 7
Bump json5, ts-loader, webpack and webpack-cli
Bumps json5 to 2.2.3 and updates ancestor dependencies json5, ts-loader, webpack and webpack-cli. These dependencies need to be updated together.

Updates json5 from 1.0.1 to 2.2.3

Release notes

Sourced from json5's releases.

v2.2.3

Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2

Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1

Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0

New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

v2.1.3 [code, diff]

Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2

Fix: Bump minimist to v1.2.5. (#222)

v2.1.1

New: package.json and package.json5 include a module property so bundlers like webpack, rollup and parcel can take advantage of the ES Module build. (#208)

Fix: stringify outputs \0 as \\x00 when followed by a digit. (#210)

Fix: Spelling mistakes have been fixed. (#196)

v2.1.0

New: The index.mjs and index.min.mjs browser builds in the dist directory support ES6 modules. (#187)

v2.0.1

Fix: The browser builds in the dist directory support ES5. (#182)

v2.0.0

Major: JSON5 officially supports Node.js v6 and later. Support for Node.js v4 has been dropped. Since Node.js v6 supports ES5 features, the code has been rewritten in native ES5, and the dependence on Babel has been eliminated.

New: Support for Unicode 10 has been added.

New: The test framework has been migrated from Mocha to Tap.

New: The browser build at dist/index.js is no longer minified by default. A minified version is available at dist/index.min.js. (#181)

Fix: The warning has been made clearer when line and paragraph separators are

... (truncated)

Changelog

Sourced from json5's changelog.

v2.2.3 [code, diff]

Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2 [code, diff]

Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1 [code, diff]

Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0 [code, diff]

New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

v2.1.3 [code, diff]

Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2 [code, diff]

Fix: Bump minimist to v1.2.5. (#222)

v2.1.1 [code, [diff][d2.1.1]]

... (truncated)

Commits

c3a7524 2.2.3

94fd06d docs: update CHANGELOG for v2.2.3

3b8cebf docs(security): use GitHub security advisories

f0fd9e1 docs: publish a security policy

6a91a05 docs(template): bug -> bug report

14f8cb1 2.2.2

10cc7ca docs: update CHANGELOG for v2.2.2

7774c10 fix: add proto to objects and arrays

edde30a Readme: slight tweak to intro

97286f8 Improve example in readme

Additional commits viewable in compare view

Updates ts-loader from 8.0.1 to 8.4.0

Release notes

Sourced from ts-loader's releases.

v8.4.0

fix: cater for change in resolveTypeReferenceDirective API in 4.7 - thanks @dragomirtitian

This is a backport from v9.2.7 for webpack 4 compatibility

v8.3.0

Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov* This is a backport from v9.2.0 for webpack 4 compatibility

v8.2.0

Use caches for module resolution and type reference directives when using compiler default functions - thanks @sheetalkamat - uses: microsoft/TypeScript#43700

This is a backport from v9.1.0 for webpack 4 compatibility - thanks @jasonkleban

v8.1.0

feat: remove top-level typescript import statements - thanks @ulivz

v8.0.18

Perf: Optimize fileExists callback path - thanks @berickson1

v8.0.17

Included correct webpack source location in emitted errors - thanks @lorenzodallavecchia

v8.0.16

Re-Fixed missing errors in watch mode in webpack5 - thanks @appzuka

v8.0.15

Update definition files in watch mode in webpack@5 - thanks @appzuka,@JonWallsten,@alexander-akait

Add afterDeclarations to getCustomTransformers in README.md - thanks @appzuka

v8.0.14

Upgrade chalk, loader-utils, and semver to latest stable versions - thanks Avi Vahl

v8.0.13

Speed up builds by adding an in-memory cache to file path lookups - thanks @berickson1

v8.0.12

Instead of checking date, check time thats more accurate to see if something has changed - thanks @sheetalkamat

v8.0.11

Fixed build failing in yarn v2 pnp - @aicest

v8.0.10

Fixed missing errors in watch mode in webpack5 - thanks @appzuka

v8.0.9

Fixed build failing when using thread-loader - thanks @valerio

v8.0.8

Fixed memory leak when using multiple webpack instances - thanks @valerio

v8.0.7

... (truncated)

Changelog

Sourced from ts-loader's changelog.

v8.4.0

fix: cater for change in resolveTypeReferenceDirective API in 4.7 - thanks @dragomirtitian

This is a backport from v9.2.7 for webpack 4 compatibility

v8.3.0

Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov

This is a backport from v9.2.0 for webpack 4 compatibility

v8.2.0

Use caches for module resolution and type reference directives when using compiler default functions - thanks @sheetalkamat - uses: microsoft/TypeScript#43700

This is a backport from v9.1.0 for webpack 4 compatibility

v8.1.0

feat: remove top-level typescript import statements - thanks @ulivz

Commits

ef85a62 fix: cater for change in resolveTypeReferenceDirective API in 4.7 (#1446)

3639cbd Backport #1317 to v8 (#1319)

6787a39 Backport #1287 to v8 (#1291)

8a32b04 docs: remove reference to travis and appveyor

dc99b31 Fix 'Usage with webpack watch' code example syntax (#1280)

0d6c803 run comparison tests in consistent location on Windows (#1277)

a1b19a1 feat: remove top-level typescript import statements (#1259)

656d6b8 Drop Travis (#1267)

c2c1aef Optimize fileExists callback path (#1266)

953358e Stop testing TypeScript 3.6 and 3.7

Additional commits viewable in compare view

Updates webpack from 4.43.0 to 5.75.0

Release notes

Sourced from webpack's releases.

v5.75.0

Bugfixes

experiments.* normalize to false when opt-out

avoid NaN%

show the correct error when using a conflicting chunk name in code

HMR code tests existance of window before trying to access it

fix eval-nosources-* actually exclude sources

fix race condition where no module is returned from processing module

fix position of standalong semicolon in runtime code

Features

add support for @import to extenal CSS when using experimental CSS in node

add i64 support to the deprecated WASM implementation

Developer Experience

expose EnableWasmLoadingPlugin

add more typings

generate getters instead of readonly properties in typings to allow overriding them

v5.74.0

Features

add resolve.extensionAlias option which allows to alias extensions

This is useful when you are forced to add the .js extension to imports when the file really has a .ts extension (typescript + "type": "module")

add support for ES2022 features like static blocks

add Tree Shaking support for ProvidePlugin

Bugfixes

fix persistent cache when some build dependencies are on a different windows drive

make order of evaluation of side-effect-free modules deterministic between concatenated and non-concatenated modules

remove left-over from debugging in TLA/async modules runtime code

remove unneeded extra 1s timestamp offset during watching when files are actually untouched

This sometimes caused an additional second build which are not really needed

fix shareScope option for ModuleFederationPlugin

set "use-credentials" also for same origin scripts

Performance

Improve memory usage and performance of aggregating needed files/directories for watching

This affects rebuild performance

Extensibility

export HarmonyImportDependency for plugins

v5.73.0

... (truncated)

Commits

8241da7 5.75.0

a91d923 Merge pull request #16458 from webpack/bugfix/semi

4608b11 Merge pull request #16457 from webpack/tooling/update

dfdd0b0 Merge pull request #16122 from AnmolBansalDEV/bug/compilationCallback

23b9a1c Merge pull request #16167 from exposir/fixts

6f2c5e8 Merge pull request #16257 from alexzhang1030/calc_deterministic_verbose

f7f36ad Merge pull request #16339 from Liamolucko/wasm-i64

761a542 fix semicolon position

2403a36 Merge pull request #16345 from ahabhgk/fix-eval-nosources

c18203c update tooling

Additional commits viewable in compare view

Updates webpack-cli from 3.3.12 to 5.0.1

Release notes

Sourced from webpack-cli's releases.

v5.0.1

5.0.1 (2022-12-05)

Bug Fixes

make define-process-env-node-env alias node-env (#3514) (346a518)

v5.0.0

5.0.0 (2022-11-17)

Bug Fixes

improve description of the --disable-interpret option (#3364) (bdb7e20)

remove the redundant utils export (#3343) (a9ce5d0)

respect NODE_PATH env variable (#3411) (83d1f58)

show all CLI specific flags in the minimum help output (#3354) (35843e8)

Features

failOnWarnings option (#3317) (c48c848)

update commander to v9 (#3460) (6621c02)

added the --define-process-env-node-env option

update interpret to v3 and rechoir to v0.8

add an option for preventing interpret (#3329) (c737383)

BREAKING CHANGES

the minimum supported webpack version is v5.0.0 (#3342) (b1af0dc), closes #3342

webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0

webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0

remove the migrate command (#3291) (56b43e4), closes #3291

remove the --prefetch option in favor the PrefetchPlugin plugin

remove the --node-env option in favor --define-process-env-node-env

remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)

the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

v4.10.0

4.10.0 (2022-06-13)

Bug Fixes

changeTime is already in milliseconds (#3198) (d390d32)

improve parsing of --env flag (#3286) (402c0fe)

Features

added types (8ec1375)

v4.9.2

4.9.2 (2022-01-24)

... (truncated)

Changelog

Sourced from webpack-cli's changelog.

5.0.1 (2022-12-05)

Bug Fixes

make define-process-env-node-env alias node-env (#3514) (346a518)

5.0.0 (2022-11-17)

Bug Fixes

improve description of the --disable-interpret option (#3364) (bdb7e20)

remove the redundant utils export (#3343) (a9ce5d0)

respect NODE_PATH env variable (#3411) (83d1f58)

show all CLI specific flags in the minimum help output (#3354) (35843e8)

Features

failOnWarnings option (#3317) (c48c848)

update commander to v9 (#3460) (6621c02)

added the --define-process-env-node-env option

update interpret to v3 and rechoir to v0.8

add an option for preventing interpret (#3329) (c737383)

BREAKING CHANGES

the minimum supported webpack version is v5.0.0 (#3342) (b1af0dc), closes #3342

webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0

webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0

remove the migrate command (#3291) (56b43e4), closes #3291

remove the --prefetch option in favor the PrefetchPlugin plugin

remove the --node-env option in favor --define-process-env-node-env

remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)

the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

4.10.0 (2022-06-13)

Bug Fixes

changeTime is already in milliseconds (#3198) (d390d32)

improve parsing of --env flag (#3286) (402c0fe)

Features

added types (8ec1375)

4.9.2 (2022-01-24)

Bug Fixes

respect negatedDescription for flags from schema (#3102) (463b731)

... (truncated)

Commits

4a0f893 chore(release): publish new version

9de982c chore: fix cspell

32d26c8 chore(deps-dev): bump cspell from 6.15.1 to 6.16.0 (#3517)

2788bf9 chore(deps-dev): bump eslint from 8.28.0 to 8.29.0 (#3516)

ac88ee4 chore(deps-dev): bump lint-staged from 13.0.4 to 13.1.0 (#3515)

346a518 fix: make define-process-env-node-env alias node-env (#3514)

3ec7b16 chore(deps): bump yeoman-environment from 3.12.1 to 3.13.0 (#3508)

c8adfa6 chore(deps-dev): bump @types/node from 18.11.9 to 18.11.10 (#3513)

0ad8cc2 chore(deps-dev): bump cspell from 6.15.0 to 6.15.1 (#3512)

d30f261 chore(deps-dev): bump ts-loader from 9.4.1 to 9.4.2 (#3511)

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump flat and mocha
Bumps flat to 5.0.2 and updates ancestor dependency mocha. These dependencies need to be updated together.

Updates flat from 4.1.0 to 5.0.2

Commits

e5ffd66 Release 5.0.2

fdb79d5 Update dependencies, refresh lockfile, format with standard.

e52185d Test against node 14 in CI.

0189cb1 Avoid arrow function syntax.

f25d3a1 Release 5.0.1

54cc7ad use standard formatting

779816e drop dependencies

2eea6d3 Bump lodash from 4.17.15 to 4.17.19

a61a554 Bump acorn from 7.1.0 to 7.4.0

20ef0ef Fix prototype pollution on unflatten

Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by timoxley, a new releaser for flat since your current version.

Updates mocha from 7.1.2 to 10.2.0

Release notes

Sourced from mocha's releases.

v10.2.0

10.2.0 / 2022-12-11

:tada: Enhancements

#4945: API: add possibility to decorate ESM name before import (@j0tunn)

:bug: Fixes

#4946: Browser: color of failed test icon (@kleisauke)

:book: Documentation

#4944: Remove duplicated header (@PauloGoncalvesBH)

v10.1.0

10.1.0 / 2022-10-16

:tada: Enhancements

#4896: Browser: add support for prefers-color-scheme: dark (@greggman)

:nut_and_bolt: Other

#4912: Browser: increase contrast for replay buttons (@JoshuaKGoldberg)

#4905: Use standard Promise.allSettled instead of polyfill (@outsideris)

#4899: Upgrade official GitHub actions to latest (@ddzz)

#4770: Fix regex in function clean(@yetingli)

v10.0.0

10.0.0 / 2022-05-01

:boom: Breaking Changes

#4845: Drop Node.js v12.x support (@juergba)

#4848: Drop Internet-Explorer-11 support (@juergba)

#4857: Drop AMD/RequireJS support (@juergba)

#4866: Drop Growl notification support (@juergba)

#4863: Rename executable bin/mocha to bin/mocha.js (@juergba)

#4865: --ignore option in Windows: upgrade Minimatch (@juergba)

#4861: Remove deprecated Runner signature (@juergba)

:nut_and_bolt: Other

... (truncated)

Changelog

Sourced from mocha's changelog.

10.2.0 / 2022-12-11

:tada: Enhancements

#4945: API: add possibility to decorate ESM name before import (@j0tunn)

:bug: Fixes

#4946: Browser: color of failed test icon (@kleisauke)

:book: Documentation

#4944: Remove duplicated header (@PauloGoncalvesBH)

10.1.0 / 2022-10-16

:tada: Enhancements

#4896: Browser: add support for prefers-color-scheme: dark (@greggman)

:nut_and_bolt: Other

#4912: Browser: increase contrast for replay buttons (@JoshuaKGoldberg)

#4905: Use standard Promise.allSettled instead of polyfill (@outsideris)

#4899: Upgrade official GitHub actions to latest (@ddzz)

#4770: Fix regex in function clean(@yetingli)

10.0.0 / 2022-05-01

:boom: Breaking Changes

#4845: Drop Node.js v12.x support (@juergba)

#4848: Drop Internet-Explorer-11 support (@juergba)

#4857: Drop AMD/RequireJS support (@juergba)

#4866: Drop Growl notification support (@juergba)

#4863: Rename executable bin/mocha to bin/mocha.js (@juergba)

#4865: --ignore option in Windows: upgrade Minimatch (@juergba)

#4861: Remove deprecated Runner signature (@juergba)

:nut_and_bolt: Other

#4878: Update production dependencies (@juergba)

#4876: Add Node.js v18 to CI test matrix (@outsideris)

... (truncated)

Commits

202e9b8 build(v10.2.0): release

6782d6d build(v10.2.0): update CHANGELOG

73bb819 feat(esm): ability to decorate ESM module name before importing it (#4945)

fc4ac58 chore(devDeps): remove unused depedencies (#4949)

0a10ddc docs: remove duplicated header (#4944)

b0a0fb8 fix(browser): failed test icon color (#4946)

3cc9cac ci: update stale action (#4931)

8f3c37b chore(ci): workaround for firefox error (#4933)

5f96d51 build(v10.1.0): release

ed74f16 build(v10.1.0): update CHANGELOG

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Please add support for `cargo add` and `cargo remove` commands

Similarly to the cargo fetch and cargo update commands, which currently can be run from within VS Code, it would be very convenient to add support for cargo add and cargo remove commands, respectively to add and remove dependencies.

Note: cargo add was introduced with Rust 1.62, and cargo remove was introduced just today with Rust 1.66. These two commands were first implemented in cargo edit. In future other commands from cargo edit may be integrated into Cargo, such as cargo upgrade.

opened by lucatrv 0
Bump qs from 6.5.2 to 6.5.3
Bumps qs from 6.5.2 to 6.5.3.

Changelog

Sourced from qs's changelog.

6.5.3

[Fix] parse: ignore __proto__ keys (#428)

[Fix] utils.merge`: avoid a crash with a null target and a truthy non-array source

[Fix] correctly parse nested arrays

[Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (#279)

[Fix] utils: merge: fix crash when source is a truthy primitive & no options are provided

[Fix] when parseArrays is false, properly handle keys ending in []

[Fix] fix for an impossible situation: when the formatter is called with a non-string value

[Fix] utils.merge: avoid a crash with a null target and an array source

[Refactor] utils: reduce observable [[Get]]s

[Refactor] use cached Array.isArray

[Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (#269)

[Refactor] parse: only need to reassign the var once

[Robustness] stringify: avoid relying on a global undefined (#427)

[readme] remove travis badge; add github actions/codecov badges; update URLs

[Docs] Clean up license text so it’s properly detected as BSD-3-Clause

[Docs] Clarify the need for "arrayLimit" option

[meta] fix README.md (#399)

[meta] add FUNDING.yml

[actions] backport actions from main

[Tests] always use String(x) over x.toString()

[Tests] remove nonexistent tape option

[Dev Deps] backport from main

Commits

298bfa5 v6.5.3

ed0f5dc [Fix] parse: ignore __proto__ keys (#428)

691e739 [Robustness] stringify: avoid relying on a global undefined (#427)

1072d57 [readme] remove travis badge; add github actions/codecov badges; update URLs

12ac1c4 [meta] fix README.md (#399)

0338716 [actions] backport actions from main

5639c20 Clean up license text so it’s properly detected as BSD-3-Clause

51b8a0b add FUNDING.yml

45f6759 [Fix] fix for an impossible situation: when the formatter is called with a no...

f814a7f [Dev Deps] backport from main

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Bump decode-uri-component from 0.2.0 to 0.2.2
Bumps decode-uri-component from 0.2.0 to 0.2.2.

Release notes

Sourced from decode-uri-component's releases.

v0.2.2

Prevent overwriting previously decoded tokens 980e0bf

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

v0.2.1

Switch to GitHub workflows 76abc93

Fix issue where decode throws - fixes #6 746ca5d

Update license (#1) 486d7e2

Tidelift tasks a650457

Meta tweaks 66e1c28

https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

Commits

a0eea46 0.2.2

980e0bf Prevent overwriting previously decoded tokens

3c8a373 0.2.1

76abc93 Switch to GitHub workflows

746ca5d Fix issue where decode throws - fixes #6

486d7e2 Update license (#1)

a650457 Tidelift tasks

66e1c28 Meta tweaks

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 0
Optional italic decorators and/or configurable margin

Hey, the extension is great and does exactly what it says. I could try to implement this feature myself, but I have zero experience with developing vscode extensions. Onto the suggestion now.

Is your feature request related to a problem? Please describe. It would be nice to have the option to make the decorators italic. In my opinion this looks nice, and makes it slightly more distinguishable from the actual content in the editor. As a bonus configurable margin for the decorators would be great too.

Describe the solution you'd like Simple setting entries allowing the said behaviour, here's an example from settings.json of achieving such on the Error Lens extension: "errorLens.fontStyleItalic": true, "errorLens.margin": "10ch"

Describe alternatives you've considered Maybe the italic font could also be achieved with a tag based approach, similar to HTML's i or em tags. Not sure how intuitive that would be...

Additional context This doesn't necessarily seem that useful of a feature with the default emoji decorators, but it can have an effect with other decorators, such as my incompatibleDecorator "latest: ${version}". Would also help with visual consistency regarding other extensions such as Error Lens where such behaviour can be achieved easily.

opened by Strikeless 0

Releases(0.5.6)

0.5.6(Feb 13, 2021)
Comma handled for ranged versions #117

Fix for comments with brackets inside arrays #115

${version} is not being replaced for compatible decorator #118

Support alternative local index #109

Source code(tar.gz)
Source code(zip)
0.5.2(Jul 17, 2020)

Source code(tar.gz)
Source code(zip)
0.5.1(Jul 3, 2020)
Local registry index PR merged thanks to ervinoro

New setting added "crates.useLocalCargoIndex" to switch between GithHub and Local index.

local index path bug fixed #82

crew.dev support and cleaner popup design #72

Source code(tar.gz)
Source code(zip)
0.4.9(Mar 16, 2020)

vscodeignore fixed
Source code(tar.gz)
Source code(zip)
0.4.8(Mar 16, 2020)
Go to DOCS.RS added in popup #72

"0.0.0" version is included now #73

Source code(tar.gz)
Source code(zip)
0.4.6(Nov 19, 2019)
Should not convert single to double quotes #66

Rate limiting should not trigger error messages #65

Fetch Errors and constant error messages when viewing Cargo.toml with conflicts #61

Alert always happen when I add deps to Cargo.toml #59

No versions found error should be less intrusive #58

alternative registries are not taken into account #41

Source code(tar.gz)
Source code(zip)
0.5.5(Nov 5, 2019)
Github basic authentication support for increasing api rates 5000req/h #60

Source code(tar.gz)
Source code(zip)
0.4.4(Oct 15, 2019)
Dependencies updated.

Certain version numbers cause fetch errors. #37

Buggy rendering for parameterized dependencies #52

^ versions handled incorrectly #39

Splitting vscode package into @types/vscode and vscode-test #57

Uppercase key seems to be causing an error #56

Source code(tar.gz)
Source code(zip)
0.4.2(Apr 8, 2019)
Sorting is now uses version compare. #45 Thanks to kupiakos

Yanked versions fixed. #44

Source code(tar.gz)
Source code(zip)
0.4.1(Apr 5, 2019)
Sorting of the versions fixed. #43

Source code(tar.gz)
Source code(zip)
0.4.0(Mar 15, 2019)
All fetches will be done from github api to crates.io-index repository . #42.

Dependencies updated.

Quoted dependency names are supported now. #40.

Source code(tar.gz)
Source code(zip)
0.3.7(Feb 12, 2019)

package alias support
Source code(tar.gz)
Source code(zip)
0.3.6(Dec 11, 2018)

Source code(tar.gz)
Source code(zip)
0.3.5(Oct 31, 2018)

Source code(tar.gz)
Source code(zip)
0.3.4(Oct 23, 2018)

Source code(tar.gz)
Source code(zip)
0.3.3(Oct 10, 2018)

Source code(tar.gz)
Source code(zip)
0.2.4(Jul 19, 2018)

Source code(tar.gz)
Source code(zip)
0.2.3(Jul 15, 2018)
Extension listener is back to onchange but with a dirty control #15.

Out of line dependencies supported. #8.

No dependency case handled by @userzimmermann

Source code(tar.gz)
Source code(zip)
0.2.2(Jul 13, 2018)
"-" is the controlidentifier for pre-release check.

crates now decorates the toml file on each save. Not on every change.

Invalid toml files caused a glitch on version decorations. Now all will be cleared with a toolbar and error message. Also commented sections handled correctly. #9

Source code(tar.gz)
Source code(zip)
0.2.1(Jul 4, 2018)

Source code(tar.gz)
Source code(zip)
0.2.0(Jul 2, 2018)
Version resolution support improved #6.

Yanked versions removed from the version list #7.

Source code(tar.gz)
Source code(zip)
0.1.1(Jun 19, 2018)

Source code(tar.gz)
Source code(zip)
release/0.0.10(May 16, 2018)

Source code(tar.gz)
Source code(zip)

crates is an extension aims to help people to manage their dependencies for rust (crates.io & TOML).

Related tags

Overview

crates

Notes

Features

Update Single Dependency

Update All Dependencies (lazy mode)

Simple settings

Known Issues

Thanks to

Comments

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.3 [code, diff]

v2.1.2

v2.1.1

v2.1.0

v2.0.1

v2.0.0

v2.2.3 [code, diff]

v2.2.2 [code, diff]

v2.2.1 [code, diff]

v2.2.0 [code, diff]

v2.1.3 [code, diff]

v2.1.2 [code, diff]

v2.1.1 [code, [diff][d2.1.1]]

v8.3.0

v8.2.0

v8.1.0

v8.0.18

v8.0.17

v8.0.16

v8.0.15

v8.0.14

v8.0.13

v8.0.12

v8.0.11

v8.0.10

v8.0.9

v8.0.8

v8.0.7

v8.4.0

v8.3.0

v8.2.0

v8.1.0

v5.75.0

Bugfixes

Features

Developer Experience

v5.74.0

Features

Bugfixes

Performance

Extensibility

v5.73.0

v5.0.1

5.0.1 (2022-12-05)

Bug Fixes

v5.0.0

5.0.0 (2022-11-17)

Bug Fixes

Features

BREAKING CHANGES

v4.10.0

4.10.0 (2022-06-13)

Bug Fixes

Features

v4.9.2

4.9.2 (2022-01-24)

5.0.1 (2022-12-05)

Bug Fixes

5.0.0 (2022-11-17)

Bug Fixes

Features

BREAKING CHANGES

4.10.0 (2022-06-13)

Bug Fixes