microsoft / microsoft/playwright-dotnet
[Feature]: Remove NodeJS runtime from package
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3k
- Forks
- 304
- Avg merge
- 20h 47m
- Merged PRs (30d)
- 6
Description
Feature request
Please, remove NodeJS runtime from a nuget package.
NodeJs could be included in separate nuget package out of convenience. Playwright could use environment variable to determine path to node binaries.
The problem
Including a NodeJS binaries slows down a CI/CD pipeline.
It has to be restored on each build (Azure Hosted pipeline).
Given that I have multiple projects referencing playwright, I have a gigabyte of unnecessary binaries that I have to upload as build artifacts and downloads in my release pipeline. My CI produces 300GB of build artifacts per months with only two developers pushing the code.
Now imagine, that other nuget references would include NodeJS runtime as well!
It has to be removed or made optional.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the NuGet package contents and how the Playwright .NET package locates its NodeJS binaries; the issue names no specific files or tests. Compare the proposed separate-package and environment-variable approaches, then verify that the chosen design no longer forces NodeJS binaries into the default package while preserving a workable installation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, nodejs
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100