How long do driver versions and browser links stay active?

[supercom32]

Hi There,

I noted that when running a compiled Playwright-go application for the first time, it downloads drivers and browser versions before it start. Could anyone kindly tell me how long these links remain active? Are they always present to guarentee older compiled software works? Or do they eventually go away and require the program to be built with a new version of Playwright-go linked to it?

[mxschmitt]

Hi, currently since it's still in the 0.x versioning there is no guarantee that the links stay active. But probably they will stay since they are hosted on the Microsoft CDN.

Would be awesome if you could upvote/comment this issue to help this project to grow and to have a future where the gets maintained better etc.

[supercom32]

Hi,

Thanks for the kind reply! If you have any control over this, I would humbly request that you consider keeping all versions active and online once they are published. The reason being, many projects pin libraries at specific versions for stability reasons and they depend on environments to remain stable. This is similar to how older versions of libraries never get removed from NPM or other repositories. Considering the project is still at 0.x versioning, operating guarentees and promises are even more important as to gain peoples trust and confidence to try the library and give it a shot. At the very least, perhaps a method to override and specify mirror locations for the driver, browsers, ffmpeg, etc could be made. That way, if playwright-go is somehow unable or unwilling to do it, people can backup their own versions of the dependancies and host it themselves someplace (for download by clients if needed).

Thanks again for your time. I'll totally take a look at the other issue and comment on it appropriately!