John Firebaugh

The issue with using `optimizeDeps.exclude` for this is that this also excludes deps of that package from vite's esm/cjs interop magic. So you then have to run through and include...

Ah, true. I would also be okay with saying "test a built vsix first, then trigger the release" and having the release build and upload its own vsix. I don't...

I also support this. Thanks for your help @vogelsgesang! Can you open a PR adding yourself to CODEOWNERS?

Add Figma to the list of companies that would appreciate first class Bazel support in firebase-ios-sdk.

> However, I believe including tinyjson directly into the process_wrapper crate would work around this issue. I attempted this solution. First I tried retaining the `@rules_rust_tinyjson` repository but using `copy_file`...

By the way, does anything prevent process_wrapper itself from being susceptible to the same issue?

It's still not working for me, but with a different error. I'll open a new issue.

Looks like now CI is complaining about a code style issue. This line is exeeding 80 characters (sorry we don't have autoformatting set up yet): https://github.com/bazelbuild/vscode-bazel/blob/076e3432f306f5fd44a93a021cfea4c6a5b87ba9/src/bazel/bazel_query.ts#L132

In the other systems though, "stroke" is used to denote what we're calling "line", and there's no equivalent analog of "line-stroke". For example, in Illustrator, to create effects similar to...

I would like to just remove this property and either hard-code a default, use the style global `transition` duration, or have a separate style-global value like `transition` or `light`.