Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update npm dependencies #61

Merged
merged 1 commit into from
Sep 28, 2024
Merged

chore(deps): update npm dependencies #61

merged 1 commit into from
Sep 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@playwright/test (source) 1.46.1 -> 1.47.2 age adoption passing confidence
@tauri-apps/cli 1.6.1 -> 1.6.2 age adoption passing confidence
@types/node (source) 20.16.2 -> 20.16.10 age adoption passing confidence
axios (source) 1.7.6 -> 1.7.7 age adoption passing confidence
eslint (source) 8.57.0 -> 8.57.1 age adoption passing confidence
eslint-plugin-import 2.29.1 -> 2.30.0 age adoption passing confidence
eslint-plugin-solid 0.14.2 -> 0.14.3 age adoption passing confidence
husky 9.1.5 -> 9.1.6 age adoption passing confidence
jsdom 24.1.1 -> 24.1.3 age adoption passing confidence
prettier-plugin-tailwindcss 0.6.6 -> 0.6.8 age adoption passing confidence
socket.io-client (source) 4.7.5 -> 4.8.0 age adoption passing confidence
solid-js (source) 1.8.22 -> 1.9.1 age adoption passing confidence
tailwindcss (source) 3.4.10 -> 3.4.13 age adoption passing confidence
typescript (source) 5.5.4 -> 5.6.2 age adoption passing confidence
vite (source) 5.4.6 -> 5.4.8 age adoption passing confidence
vitest (source) 2.0.5 -> 2.1.1 age adoption passing confidence

Release Notes

microsoft/playwright (@​playwright/test)

v1.47.2

Compare Source

Highlights

https://github.com/microsoft/playwright/pull/32699- [REGRESSION]: fix(codegen): use content_frame property in python/.NEThttps://github.com/microsoft/playwright/issues/327066- [REGRESSION]: page.pause() does not pause test timeout after 1.4https://github.com/microsoft/playwright/pull/3266161 - fix(trace-viewer): time delta between local and remote actions

Browser Versions

  • Chromium 129.0.6668.29
  • Mozilla Firefox 130.0
  • WebKit 18.0

This version was also tested against the following stable channels:

  • Google Chrome 128
  • Microsoft Edge 128

v1.47.1

Compare Source

v1.47.0

Compare Source

tauri-apps/tauri (@​tauri-apps/cli)

v1.6.2: @​tauri-apps/cli v1.6.2

Compare Source

[1.6.2]

Dependencies
  • Upgraded to tauri-cli@1.6.2
axios/axios (axios)

v1.7.7

Compare Source

Bug Fixes
  • fetch: fix stream handling in Safari by fallback to using a stream reader instead of an async iterator; (#​6584) (d198085)
  • http: fixed support for IPv6 literal strings in url (#​5731) (364993f)
Contributors to this release
eslint/eslint (eslint)

v8.57.1

Compare Source

import-js/eslint-plugin-import (eslint-plugin-import)

v2.30.0

Compare Source

Added
Fixed
Changed
  • [Docs] no-extraneous-dependencies: Make glob pattern description more explicit ([#​2944], thanks [@​mulztob])
  • [no-unused-modules]: add console message to help debug [#​2866]
  • [Refactor] ExportMap: make procedures static instead of monkeypatching exportmap ([#​2982], thanks [@​soryy708])
  • [Refactor] ExportMap: separate ExportMap instance from its builder logic ([#​2985], thanks [@​soryy708])
  • [Docs] order: Add a quick note on how unbound imports and --fix ([#​2640], thanks [@​minervabot])
  • [Tests] appveyor -> GHA (run tests on Windows in both pwsh and WSL + Ubuntu) ([#​2987], thanks [@​joeyguerra])
  • [actions] migrate OSX tests to GHA ([ljharb#37], thanks [@​aks-])
  • [Refactor] exportMapBuilder: avoid hoisting ([#​2989], thanks [@​soryy708])
  • [Refactor] ExportMap: extract "builder" logic to separate files ([#​2991], thanks [@​soryy708])
  • [Docs] [order]: update the description of the pathGroupsExcludedImportTypes option ([#​3036], thanks [@​liby])
  • [readme] Clarify how to install the plugin ([#​2993], thanks [@​jwbth])
solidjs-community/eslint-plugin-solid (eslint-plugin-solid)

v0.14.3

Compare Source

What's Changed

New Contributors

Full Changelog: solidjs-community/eslint-plugin-solid@v0.14.2...v0.14.3

typicode/husky (husky)

v9.1.6

Compare Source

jsdom/jsdom (jsdom)

v24.1.3

Compare Source

  • Fixed calls to postMessage() that were done as a bare property (i.e., postMessage() instead of window.postMessage()).

v24.1.2

Compare Source

  • Fixed an issue with the in operator applied to EventTarget methods, e.g. 'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)
  • Fixed the events fired by blur(): it no longer fires focus and focusin on the Document, and blur and focusout no longer have their relatedTarget property set. (asamuzaK)
tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.6.8

Compare Source

v0.6.7

Compare Source

  • Improved performance with large Svelte, Liquid, and Angular files (#​312)
  • Add support for @plugin and @config in v4 (#​316)
  • Add support for Tailwind CSS v4.0.0-alpha.25 (#​317)
socketio/socket.io (socket.io-client)

v4.8.0

Compare Source

Features
Custom transport implementations

The transports option now accepts an array of transport implementations:

import { io } from "socket.io-client";
import { XHR, WebSocket } from "engine.io-client";

const socket = io({
  transports: [XHR, WebSocket]
});

Here is the list of provided implementations:

Transport Description
Fetch HTTP long-polling based on the built-in fetch() method.
NodeXHR HTTP long-polling based on the XMLHttpRequest object provided by the xmlhttprequest-ssl package.
XHR HTTP long-polling based on the built-in XMLHttpRequest object.
NodeWebSocket WebSocket transport based on the WebSocket object provided by the ws package.
WebSocket WebSocket transport based on the built-in WebSocket object.
WebTransport WebTransport transport based on the built-in WebTransport object.

Usage:

Transport browser Node.js Deno Bun
Fetch ✅ ✅ (1) ✅ ✅
NodeXHR ✅ ✅ ✅
XHR ✅
NodeWebSocket ✅ ✅ ✅
WebSocket ✅ ✅ (2) ✅ ✅
WebTransport ✅ ✅

(1) since v18.0.0
(2) since v21.0.0

Added in f4d898e and b11763b.

Test each low-level transports

When setting the tryAllTransports option to true, if the first transport (usually, HTTP long-polling) fails, then the other transports will be tested too:

import { io } from "socket.io-client";

const socket = io({
  tryAllTransports: true
});

This feature is useful in two cases:

  • when HTTP long-polling is disabled on the server, or if CORS fails
  • when WebSocket is tested first (with transports: ["websocket", "polling"])

The only potential downside is that the connection attempt could take more time in case of failure, as there have been reports of WebSocket connection errors taking several seconds before being detected (that's one reason for using HTTP long-polling first). That's why the option defaults to false for now.

Added in 579b243.

Bug Fixes
  • accept string | undefined as init argument (bis) (60c757f)
  • allow to manually stop the reconnection loop (13c6d2e)
  • close the engine upon decoding exception (04c8dd9)
  • do not send a packet on an expired connection (#​5134) (8adcfbf)
Dependencies
solidjs/solid (solid-js)

v1.9.0: - LGTM!

Compare Source

This release like the last is focusing on small quality of life improvements and adjustments that will help us move towards 2.0. So while not the most exciting release to everyone it provides some really important features and fixes to some developers.

And unlike many previous releases the vast majority of the work and features came from PRs from the community. So really all I can say is Looks Good to Me!

Better JSX Validation

While still incomplete across templates we've added JSDOM to the compiler to better detect invalid HTML at build time by comparing what we expect the template to be with what a browser would output. This now includes things that are nested we didn't detect before like putting <a> inside other <a> tags which will lead to the browser "correcting" it in less than intuitive ways.

Improved Exports

While each environment in solid-js/web has its own methods to be used in the compiler. We are now exporting the client methods from the server to prevent weird import errors. Now these methods will throw if used in this environment but shouldn't break your build.

Additionally we have seen some issues in bundlers that incorrectly feed our ESM exports back through the browser field. While this is a known issue they all pointed issues at each other and with no intention of fixing it. We have removed the browser field in this release, meaning some legacy packages may have issues resolving browser if they don't support export conditions.

This is regretful but this blocked deployments on several platforms and since this was the only fix at our disposal after two years of attempting to push this issue to the bundlers to no avail, we've moved forward with it.

Custom Element improvements

We have a few improvements to our custom element support in this release. First off we now detect elements with the is attribute as custom elements which means all the special behavior is afforded to them.

We've also improved our event handler delegating retargetting to better handle shadow DOM events. There were cases where we skipped over part of the tree.

Finally we've added the bool: attribute namespace to handle explicitly setting certain attributes according to boolean attribute rules. While this isn't necessary for built-in booleans currently we handle most attributes as properties and we lacked a specific override. But now we have it:

<my-element bool:enable={isEnabled()}></my-element>

Support for handleEvent Syntax in Non-Delegated Events

A little known thing is that events actually also support objects instead of functions (See: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)

We(thanks @​titoBouzout) realized we can use this mechanism as a way to set advanced rules like passive or capture on this object as way to handle all current and future event attributes that browsers might add. This way we don't need specific mechanisms like oncapture: (which is now deprecated).

Instead using on: you can set the event properties you wish.

<>
  <div on:click={{
    handleEvent(e) {
      console.log("clicked", e)
    },
    once:true
  }/>
  <div on:wheel={{
    handleEvent(e) {
      e.preventDefault() // only works on not passive events
      e.stopPropagation()  
      console.log("wheel stopped?")
    },
    passive: false
  }} />
</>

Other Updates

We've fixed an issue with lazy images. Apparently, cloneNode doesn't handle them properly so we've updated our heuristic to treat templates with lazy images to be handled with importNode.

We've improved our Hydration Mismatch Error to output the template of that it can't find the matching ID for. This should make it easier to track down where the hydration errors are occurring. There have been several hydration improvements over the later 1.8 releases so upgrading will likely improve the situation for those who have been facing issues.

Finally, we've improved some of the types in the JSX and Signal Setter in this release.

Big thanks to those who contributed to this release: @​wkelly17, @​olivercoad, @​titoBouzout, @​trusktr, @​Huliiiiii. And thanks to all of you who gave feedback on the Metadata/Head Tag RFC. While it didn't make it in this time around you've definitely given us stuff to consider for its future design.

Best,
@​ryansolid

v1.8.23

Compare Source

tailwindlabs/tailwindcss (tailwindcss)

v3.4.13

Compare Source

Fixed
  • Improve source glob verification performance (#​14481)

v3.4.12

Compare Source

v3.4.11

Compare Source

microsoft/TypeScript (typescript)

v5.6.2

Compare Source

vitejs/vite (vite)

v5.4.8

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.7

Compare Source

Please refer to CHANGELOG.md for details.

vitest-dev/vitest (vitest)

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "every weekend before 5:00am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-dependencies branch 11 times, most recently from 80de6df to 048d50b Compare September 5, 2024 23:09
@renovate renovate bot force-pushed the renovate/npm-dependencies branch 11 times, most recently from df3e458 to 90cfbf7 Compare September 16, 2024 16:03
@renovate renovate bot force-pushed the renovate/npm-dependencies branch 6 times, most recently from 3a2a802 to 4f4da09 Compare September 23, 2024 17:21
@renovate renovate bot force-pushed the renovate/npm-dependencies branch 10 times, most recently from 4a2fed5 to 150e424 Compare September 28, 2024 11:03
@Ekhorn Ekhorn merged commit 925d074 into main Sep 28, 2024
10 checks passed
@Ekhorn Ekhorn deleted the renovate/npm-dependencies branch September 28, 2024 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies npm
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Ekhorn