Stop Supporting a Node Version Prior to End-Of-Life?
Do you foresee <:playwright:1054714813638516757> ending support for any versions of Node prior to version's end-of-life?
-
Node versions Playwright team recommends against 🙅 ?
-
Node versions Playwright team recommends <:doublethumbs:1071973661428428840>?
Currently Upgrading Node as our version reached EOL ⚰️ April 30, 2023 & is no longer supported by Playwright
(Angular, Typescript, .Net, Azure)
This thread is trying to answer question "Do you foresee Playwright ending support for any versions of Node prior to version's end-of-life?"
Believe most of this in in the docs as to what is supported? https://playwright.dev/docs/intro#system-requirements
Thank you! That is helpful. I'm curious if there are any future plans to stop supporting certain Node versions before the version reaches End-of-Life?
Might be more direct and ask/check here: https://github.com/microsoft/playwright/discussions
Thanks for the help! I combed through the repo for an answer and eventually posted a feature request 😄 https://github.com/microsoft/playwright/issues/24103#issue-1794001010
Related Ask AI answer for "What is Playwright's policy on supporting older versions of Node.js?".
Answer
The information provided doesn't specify if Playwright will stop supporting any versions of Node.js before their end-of-life. However, it's clear that Node.js 14 isn't supported anymore since it reached its end-of-life on April 30, 2023. This suggests that Playwright might continue to support older Node.js versions until their end-of-life.
Playwright is all about browser automation. It provides APIs to automate web browsers like Chromium, Firefox, and WebKit. The goal is to offer a consistent API across different browser versions and platforms. The current release of Playwright supports Chromium 114.0.5735.26, Mozilla Firefox 113.0, and WebKit 16.4.
Playwright also takes care of packages that need specific browsers. It does garbage collection when you update to newer Playwright versions. This way, it removes unused browser versions and saves disk space.
While there's no direct mention of future plans for Node.js version support, it's always a good idea to stay updated. Use the latest releases and follow software development best practices. This means using supported and actively maintained software versions.
In short, there's no sign that Playwright will stop supporting any specific Node.js version before its end-of-life. But it's a good idea to stay updated with Playwright's official documentation or community channels. This way, you'll be the first to know about any changes to supported Node.js versions in future releases.
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email luc@ray.run.