Skip to content
This repository has been archived by the owner on Mar 26, 2024. It is now read-only.

chore(deps): update all (major) #225

Open
wants to merge 150 commits into
base: main
Choose a base branch
from
Open

chore(deps): update all (major) #225

wants to merge 150 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2021 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
actions/checkout action major v2 -> v3 age adoption passing confidence
actions/setup-node action major v2 -> v3 age adoption passing confidence
chalk dependencies major ^4.1.2 -> ^5.0.0 age adoption passing confidence
dotenv dependencies major 10.0.0 -> 16.0.3 age adoption passing confidence
dotenv-expand dependencies major 5.1.0 -> 10.0.0 age adoption passing confidence
globby dependencies major ~11.0.0 -> ~13.1.0 age adoption passing confidence
globby devDependencies major ~11.0.0 -> ~13.1.0 age adoption passing confidence
jsdom dependencies major ^21.0.0 -> ^22.0.0 age adoption passing confidence
ora dependencies major ^5.4.1 -> ^6.0.0 age adoption passing confidence
react-error-boundary devDependencies major ^3.1.4 -> ^4.0.0 age adoption passing confidence
typescript (source) devDependencies major ^4.9.4 -> ^5.0.0 age adoption passing confidence

Release Notes

actions/checkout

v3

Compare Source

actions/setup-node

v3

Compare Source

chalk/chalk

v5.2.0

Compare Source

v5.1.2

Compare Source

v5.1.1

Compare Source

  • Improved the names of exports introduced in 5.1.0 (#​567) 6e0df05
    • We of course preserved the old names.

v5.1.0

Compare Source

v5.0.1

Compare Source

  • Add main field to package.json for backwards compatibility with some developer tools 85f7e96

v5.0.0

Compare Source

Breaking
  • This package is now pure ESM. Please read this.
    • If you use TypeScript, you need to use TypeScript 4.7 or later. Why.
    • If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.
    • The Chalk issue tracker is not a support channel for your favorite build/bundler tool.
    • It's totally fine to stay on Chalk v4. It's been stable for years.
  • Require Node.js 12.20 fa16f4e
  • Move some properties off the default export to individual named exports:
    • chalk.Instance → Chalk
    • chalk.supportsColor → supportsColor
    • chalk.stderr → chalkStderr
    • chalk.stderr.supportsColor → supportsColorStderr
  • Remove .keyword(), .hsl(), .hsv(), .hwb(), and .ansi() coloring methods (#​433) 4cf2e40
    • These were not commonly used and added a lot of bloat to Chalk. You can achieve the same by using the color-convert package.
  • The tagged template literal support moved into a separate package: chalk-template (#​524) c987c61
-import chalk from 'chalk';
+import chalkTemplate from 'chalk-template';

-chalk`2 + 3 = {bold ${2 + 3}}`;
+chalkTemplate`2 + 3 = {bold ${2 + 3}}`;
Improvements

v4.1.2

Compare Source

  • Readme updates

v4.1.1

Compare Source

v4.1.0

Compare Source

v4.0.0

Compare Source

Breaking
  • Require Node.js 10 61999a4
  • Change the Level TypeScript type to be a union instead of enum f0f4638
-if (chalk.level > Level.None) {}
+if (chalk.level > 0) {}
Improvements
  • Use Object.setPrototypeOf as __proto__ could potentially be disabled (#​387) 63469d3

v3.0.0

Compare Source

This release has been in development for more than a year and massively improves performance and the time it takes to import Chalk.

Thanks to @​stroncium for his hard work on this. 🙌

Breaking
  • Require Node.js 8 3ef170b
  • Remove the .enabled property in favor of .level (#​356) 1f77953
    • Why: It was confusing to users to have two properties for detecting color support.
    • Migrate:
-if (chalk.enabled) {}
+if (chalk.level > 0) {}
  • Remove chalk.constructor() in favor of chalk.Instance() (#​322) de2f4cd
    • Migrate:
-new chalk.constructor({level: 1});
+new chalk.Instance({level: 1})
Minor breaking
-import chalk from 'chalk';
+import chalk = require('chalk');
  • Drop built-in Flow type definition d3be9c6
    • Why: None of us use Flow and we were not good at maintaining the type definition. You can get the types at flow-typed (needs to be updated to Chalk v3, open an issue on flow-typed).
  • Rename the ChalkOptions TypeScript type to Options cf66156
  • Remove dim style workaround for Windows (#​331) cd5de7a
    • Why: The issue was fixed in newer Windows 10 builds.
  • Remove the blue color workaround for Windows (#​330) 2ca015c
    • Why: The issue was fixed in newer Windows 10 builds.
Enhancements
Color detection
Fixes
  • Fix support for nested styles (#​335) 87156ce
  • Fix const enum for TypeScript (#​364) 4e65299
  • Fix TypeScript type for supportsColor which is top‑level only (#​342) b3e9b91
  • Fix TypeScript type for chalk.supportsColor (#​347) d82b2a6
  • Fix TypeScript type for tagged template literal argument to accept unknown instead of just string (#​316) 7f6e563
motdotla/dotenv

v16.0.3

Compare Source

Changed
  • Added library version to debug logs (#​682)

v16.0.2

Compare Source

Added
  • Export env-options.js and cli-options.js in package.json for use with downstream dotenv-expand module

v16.0.1

Compare Source

Changed
  • Minor README clarifications
  • Development ONLY: updated devDependencies as recommended for development only security risks (#​658)

v16.0.0

Compare Source

Added
  • Breaking: Backtick support 🎉 (#​615)

If you had values containing the backtick character, please quote those values with either single or double quotes.

v15.0.1

Compare Source

Changed
  • Properly parse empty single or double quoted values 🐞 (#​614)

v15.0.0

Compare Source

v15.0.0 is a major new release with some important breaking changes.

Added
  • Breaking: Multiline parsing support (just works. no need for the flag.)
Changed
  • Breaking: # marks the beginning of a comment (UNLESS the value is wrapped in quotes. Please update your .env files to wrap in quotes any values containing #. For example: SECRET_HASH="something-with-a-#-hash").

..Understandably, (as some teams have noted) this is tedious to do across the entire team. To make it less tedious, we recommend using dotenv cli going forward. It's an optional plugin that will keep your .env files in sync between machines, environments, or team members.

Removed
  • Breaking: Remove multiline option (just works out of the box now. no need for the flag.)

v14.3.2

Compare Source

Changed
  • Preserve backwards compatibility on values containing # 🐞 (#​603)

v14.3.1

Compare Source

Changed
  • Preserve backwards compatibility on exports by re-introducing the prior in-place exports 🐞 (#​606)

v14.3.0

Compare Source

Added
  • Add multiline option 🎉 (#​486)

v14.2.0

Compare Source

Added
  • Add dotenv_config_override cli option
  • Add DOTENV_CONFIG_OVERRIDE command line env option

v14.1.1

Compare Source

Added
  • Add React gotcha to FAQ on README

v14.1.0

Compare Source

Added
  • Add override option 🎉 (#​595)

v14.0.1

Compare Source

Added
  • Log error on failure to load .env file (#​594)

v14.0.0

Compare Source

Added
  • Breaking: Support inline comments for the parser 🎉 (#​568)

v13.0.1

Compare Source

Changed
  • Hide comments and newlines from debug output (#​404)

v13.0.0

Compare Source

Added
  • Breaking: Add type file for config.js (#​539)

v12.0.4

Compare Source

Changed
  • README updates
  • Minor order adjustment to package json format

v12.0.3

Compare Source

Changed
  • Simplified jsdoc for consistency across editors

v12.0.2

Compare Source

Changed
  • Improve embedded jsdoc type documentation

v12.0.1

Compare Source

Changed
  • README updates and clarifications

v12.0.0

Compare Source

Removed
  • Breaking: drop support for Flow static type checker (#​584)
Changed
  • Move types/index.d.ts to lib/main.d.ts (#​585)
  • Typescript cleanup (#​587)
  • Explicit typescript inclusion in package.json (#​566)

v11.0.0

Compare Source

Changed
  • Breaking: drop support for Node v10 (#​558)
  • Patch debug option (#​550)
motdotla/dotenv-expand

v10.0.0

Compare Source

Added
  • Support special characters in default expansion (#​74)

v9.0.0

Compare Source

Added
  • Proper support for preload and cli args (#​78)

v8.0.3

Compare Source

Changed
  • 🐞 Fixed defaults bug (#​71)

v8.0.2

Compare Source

Changed
  • 🐞 Fixed preloading bug

v8.0.1

Compare Source

Added
  • Added config.js to package.json lookups

v8.0.0

Compare Source

Changed
  • Breaking: Bump to v16.0.0 of dotenv
Added
  • Preload support 🎉 (#​31)

v7.0.0

Compare Source

Changed
  • Breaking: Bump to v15.0.0 of dotenv

v6.0.1

Compare Source

Changed
  • Updated README

v6.0.0

Compare Source

Changed
  • Breaking Move default export to export of expand function (#​14b1f2)
Added
  • Add default expansion 🎉 (#​39)
  • Add missing type descriptions
sindresorhus/globby

v13.1.4

Compare Source

  • Fix error when reading inaccessible directories with gitignore: true and suppressErrors: true (#​246) e95da57
  • Remove URL TypeScript type workaround (#​230) 55a3c64

v13.1.3

Compare Source

v13.1.2

Compare Source

v13.1.1

Compare Source

v13.1.0

Compare Source

v13.0.0

Compare Source

Breaking
  • Rename generateGlobTasks to generateGlobTasksSync (#​221) 51c8f68
  • Remove ignore option for isGitIgnored and isGitIgnoredSync (#​225) 2e43cc4
    • This option never worked correctly.
Improvements
Fixes

v12.2.0

Compare Source

v12.1.0

Compare Source

v12.0.2

Compare Source

  • Ensure async method is completely async e167725

v12.0.1

Compare Source

v12.0.0

Compare Source

Breaking
  • Require Node.js 12.20 (#​181) 5c32b4a
  • This package is now pure ESM. Please read this.
  • This package now uses named exports instead of a default export
    • globby → {globby}
    • globby.sync → {globbySync}
    • globby.stream → {globbyStream}
    • globby.generateGlobTasks → {generateGlobTasks}
    • globby.hasMagic → {isDynamicPattern}
    • globby.gitignore → {isGitIgnored}
    • globby.gitignore.sync → {isGitIgnoredSync}
-const globby = require('globby');
+import {globby} from 'globby';

v11.1.0

Compare Source

  • Update dependencies to fix some npm audit notices
jsdom/jsdom

v22.1.0

Compare Source

  • Added crypto.randomUUID(). (jamesbvaughan)
  • Added DOMRect and DOMRectReadOnly.
  • Added AbortSignal.timeout().
  • Added abortSignal.throwIfAborted().
  • Added support for the submitter argument to the FormData constructor. (jenseng)
  • Improved getComputedStyle()'s results for color-based properties, to resolve named colors and attempt to provide initial inheritance support. (hoekz-wwt)
  • Updated Window's event handler properties (e.g. oncopy, ontouchstart, etc.) to reflect the latest list from the standard.
  • Fixed DOMParser-created documents to inherit their URL from the creating document.

v22.0.0

Compare Source

v21.1.2

Compare Source

  • Fixed setRangeText() used on <input> and <textarea> elements to calculate the new end index correctly. (pmstss)
  • Fixed pageX, pageY, offsetX, and offsetY on MouseEvents during dispatch. (jenseng)
  • Upgraded nwsapi to v2.2.4, bringing along various fixes to our selector engine.

v21.1.1

Compare Source

  • Fixed jsdom.reconfigure() to also adjust the URL as seen by the history API, so that e.g. history.replaceState(null, "") would not mess up the URL. (jdufresne)
  • Fixed location.hash = "" to leave any # in location.href.
  • Fixes a few bugs with CSS parsing by replacing cssom with rweb-cssom, since the latter is maintained. (seanparmelee)

v21.1.0

Compare Source

  • Added x, y, pageX, pageY, offsetX, and offsetY to MouseEvent. (jenseng, ViniciusFXavier)
  • Added support for unset with getComputedStyle(). (jsnajdr)
  • Added the submitter property to SubmitEvent. (jenseng)
  • Fixed MouseEvent's screenX and screenY to no longer coerce to integers, allowing fractional values. (jenseng)
  • Fixed formEl.submit() to not longer fire submit events. (jenseng)
  • Fixed stylesheets to no longer affect the document after their corresponding <link> is removed. (jsnajdr)
  • Fixed pointer-events to inherit when used with getComputedStyle(). (jnajdr)
  • Fixed <script> elements with no src="" to no longer fire load events. (t1ger2080)
  • Improved getComputedStyle() to cache its results, which should make it much faster. (jsnajdr)

v21.0.0

Compare Source

A potentially-breaking bug fix:

  • Fixed the window, document, location, and top properties of Window to be non-configurable. (ExE-Boss)

Other changes:

  • Added support for <input type=image> submitting forms. (jenseng)
  • Added the location setter to the Window object, which forwards to the location.href setter. Setting the URL is still only implemented for fragment navigations, however. (ExE-Boss)
  • Fixed defer="" <script> elements that are added after DOMContentLoaded to execute, instead of being skipped.
  • Fixed selectElement.selectedOptions being incorrect when optionElement.selected is set. This was a regression introduced in v20.0.1. Unfortunately this also reverts the performance improvement when appending <option> elements that was introduced then. (eps1lon)
  • Fixed the self, locationbar, menubar, personalbar, scrollbars, statusbar, toolbar, frames, parent, external, length, and screen properties of Window to be replaceable: that is, setting them will override their values, instead of having the new value be ignored. (ExE-Boss)
  • Fixed a few issues with JSDOM.fromURL() in the browser build of jsdom. (LungZeno)
sindresorhus/ora

v6.3.1

Compare Source

  • Fix Node.js 12 compatibility 4b1c2be

v6.3.0

Compare Source

v6.2.0

Compare Source

  • Add spinners export to be able to access all available spinners (#​222) f2ac111

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

  • Expose the spinner interval as a getter 447812b
  • Internal refactoring. If you use any undocumented properties, this may break for you.

v6.0.1

Compare Source

v6.0.0

Compare Source

Breaking
  • Require Node.js 12.20 ede1a54
  • This package is now pure ESM. Please read this.
  • ora.promise is now a named import called oraPromise (#​181) 9c01990
    • import {oraPromise} from 'ora';
  • oraPromise now returns the given promise instead of this (#​181) 9c01990
    • This lets you await it directly, which is more useful than chaining.
Improvements
bvaughn/react-error-boundary

v4.0.7

Compare Source

*Replaced post-processing "use client" insertion step with a custom Parcel plug-in. This should hopefully produce better source maps.

v4.0.6

Compare Source

  • Removed arrow function syntax to support older versions of Safari

v4.0.5

Compare Source

Move "use client" directive to top of the bundled file.

v4.0.4

Compare Source

README changes only

v4.0.3

Compare Source

  • withErrorBoundary forwards refs
  • Add "use client" directive

v4.0.2

Compare Source

Fix broken TypeScript definitions file (#​133, https://github.com/parcel-bundler/parcel/issues/8908)

v4.0.1

Compare Source

  • Render ErrorBoundaryContext around fallback UI as well, so the useErrorBoundary hook could be used within the fallback component to reset the boundary.

For example:

import { useErrorBoundary } from "react-error-boundary";

function ErrorFallback({ error }) {
  const { resetBoundary } = useErrorBoundary();

  return (
    <div role="alert">
      <p>Something went wrong:</p>
      <pre style={{ color: "red" }}>{error.message}</pre>
      <button onClick={resetBoundary}>Try again</button>
    </div>
  );
}

See this demo: https://codesandbox.io/s/nostalgic-browser-e9lpmf

v4.0.0

Compare Source

  • Replace useErrorHandler hook with useErrorBoundary; can be used to trigger an error boundary or dismiss one
  • Merge onReset and onResetKeys props; pass "details" object explaining the cause of the reset
Why did the useErrorHandler hook change?

The old hook had two design flaws, both related to the givenError parameter:

  1. All the hook did was throw this value. This seemed unnecessary, because if a component already has a reference to an error during render, it can just throw the value itself.
  • It would not properly re-throw null or undefined values. (Although an edge case, JavaScript enables throwing any values/types.)

If you were using the givenError functionality– you can now just throw the value directly instead.

// Before
function Greeting() {
  const [name, setName] = React.useState('')
  const {greeting, error} = useGreeting(name)
  useErrorHandler(error)
// After
function Greeting() {
  const [name, setName] = React.useState('')
  const {greeting, error} = useGreeting(name)
  if (error) {
    throw error;
  }
How can I use the new useErrorHandler hook?
Show the nearest error boundary from an event handler

React only handles errors thrown during render or during component lifecycle methods (e.g. effects and did-mount/did-update). Errors thrown in event handlers, or after async code has run, will not be caught.

This hook can be used to pass those errors to the nearest error boundary:

import { useErrorBoundary } from "react-error-boundary";

function Example() {
  const { showBoundary } = useErrorBoundary();

  useEffect(() => {
    fetchGreeting(name).then(
      response => {
        // Set data in state and re-render
      },
      error => {
        // Show error boundary
        showBoundary(error);
      }
    );
  });

  // Render ...
}
Dismiss the nearest error boundary

A fallback component can use this hook to request the nearest error boundary retry the render that original failed.

import { useErrorBoundary } from "react-error-boundary";

function ErrorFallback({ error }) {
  const { resetBoundary } = useErrorBoundary();

  return (
    <div role="alert">
      <p>Something went wrong:</p>
      <pre style={{ color: "red" }}>{error.message}</pre>
      <button onClick={resetBoundary}>Try again</button>
    </div>
  );
}
Microsoft/TypeScript

v5.0.4: TypeScript 5.0.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.0.3: TypeScript 5.0.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.0.2: TypeScript 5.0

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.9.5: TypeScript 4.9.5

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

ricokahler and others added 30 commits April 7, 2021 04:51
@ricokahler
feat: repo overhaul (#102)
2adf46f
@ricokahler
fix(build): misc build fixes
148f68c 
force version: 1.0.0-alpha.0
@ricokahler
chore(build): move emojis arounds
3955fef
@ricokahler
chore: prettier trailing comma all
1e82750
@ricokahler
chore: add yarn-error.log to gitignore
bc399d1
@ricokahler
refactor(schema-codegen): rename to generateSchemaTypes
6a13513 
Breaking Change: `generateTypes` is now `generateSchemaTypes`
@ricokahler
feat(groq-codegen): add new groq-codegen packages 🎉
62c653c
@ricokahler
fix(build): fix regex in commit analyzer
6a4fc9d
@ricokahler
feat(groq-codegen): working groq plucking! groq-codegen now includes …
e9a3dea 
…an API to pull groq from code

Breaking Change: `generateGroqTypes` has been renamed to `transformGroqToTypescript` and a combined implmentation has taken its place.

See the updated groq-codegen README for more info.
@ricokahler
feat(client): new client package!
4fb1353
@ricokahler
feat(cli): add new groq-codegen command
6a6fd20
@ricokahler
fix(types): enforce keyof T for SafeIndexedAccess
b947d50
@ricokahler
fix(build): build the client; include groq-codegen as a top-level dep
a1e962c
@ricokahler
chore: update deps
c668075
@ricokahler
chore: add babel configs for jest in workspaces
1500505
@ricokahler
refactor(types): rename ambient to common
d40a2b7
@ricokahler
refactor(schema-codegen): rename ambient to schema-codegen
c88fb94
@ricokahler
refactor(schema-codegen): update "AST" with new conventions
1c73380 
refactor(schema-codegen): update "AST" with new conventions
@ricokahler
chore: update typescript + fix deps
d72e1fa
@ricokahler
feat(groq-codegen): wip new groq-codegen method
8c2d287
@ricokahler
refactor(groq-codegen): rename getEverything to transformSchemaToType…
f5de1be 
…Node
@ricokahler
refactor(groq-codegen): update to new schema node
c0ce386
@ricokahler
refactor(groq-codegen): rename TypeNode to StructureNode; add array t…
accc22a 
…o shape
@ricokahler
refactor(groq-codegen): organize utils
4ffbb39
@ricokahler
feat(groq-codegen): add incremental hashing to structure nodes
1261cf3
@ricokahler
feat(groq-codegen): use incremental hashes for cleaner TS trees
4a3d789
@ricokahler
refactor(groq-codegen): rename canBeUndefined to canBeOptional
2abcec8
@ricokahler
feat(groq-codegen): improved null and undefined behavior
0e547cd
@ricokahler
feat(groq-codegen): support Group
c38511a
@ricokahler
test(groq-codegen): add misc TODOs/small fixes
29d8f96
@renovate renovate bot force-pushed the renovate/major-all branch from 975d9c4 to a60e218 Compare March 16, 2023 10:03
@renovate renovate bot force-pushed the renovate/major-all branch from a60e218 to 2c97793 Compare March 24, 2023 13:59
@renovate renovate bot force-pushed the renovate/major-all branch from 2c97793 to 7cf1e69 Compare March 25, 2023 01:58
@renovate renovate bot force-pushed the renovate/major-all branch from 7cf1e69 to 242f1df Compare March 25, 2023 07:20
@renovate renovate bot force-pushed the renovate/major-all branch from 242f1df to 260181d Compare March 27, 2023 19:59
@renovate renovate bot force-pushed the renovate/major-all branch from 260181d to ea288e4 Compare March 29, 2023 16:22
@renovate renovate bot force-pushed the renovate/major-all branch from ea288e4 to 102e674 Compare March 30, 2023 21:25
@renovate renovate bot force-pushed the renovate/major-all branch from 102e674 to 2bce3d7 Compare April 17, 2023 11:55
@renovate renovate bot force-pushed the renovate/major-all branch from 2bce3d7 to b2aef18 Compare April 18, 2023 07:48
@renovate renovate bot force-pushed the renovate/major-all branch from b2aef18 to 1e9cea0 Compare May 28, 2023 12:03
@renovate
Copy link
Contributor Author

renovate bot commented May 28, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@ricokahler @runeb @ochicf