You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 3, 2022. It is now read-only.
I have been toying with the idea of maintaining some sort of browser automation AST that can be compiled into various things e.g. WebPageTest scripts or Puppeteer scripts.
I realise that puppeteer/recorder has its own wrapper around puppeteer, so an AST doesn't quite fit into the current architecture. But I'd be keen on hearing your thoughts on whether this is something that is worth looking into.
The text was updated successfully, but these errors were encountered:
Hi, sorry I've been OOO for the past three weeks.
Your idea sounds great - I've thought about using an intermediate AST like representation but decided not to because it felt like a lot of additional complexity for the minimal feature set that I wanted to have for the initial prototype.
But as the project grows, I think there is a lot of value in it. I'll take a look at your repository later this week and we can see where we can take things from there :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Opening an issue off the back of this tweet.
I have been toying with the idea of maintaining some sort of browser automation AST that can be compiled into various things e.g. WebPageTest scripts or Puppeteer scripts.
I realise that puppeteer/recorder has its own wrapper around puppeteer, so an AST doesn't quite fit into the current architecture. But I'd be keen on hearing your thoughts on whether this is something that is worth looking into.
The text was updated successfully, but these errors were encountered: