George S. Baugh hace 5 años
padre
commit
031fcf262a
Se han modificado 3 ficheros con 4 adiciones y 2 borrados
  1. 2 1
      README.md
  2. 0 1
      bin/playwright.js
  3. 2 0
      lib/Playwright.pm

+ 2 - 1
README.md

@@ -9,7 +9,8 @@ Finally, a solution!
 ## Here's how it works
 
 A little node webserver written in [express][xp] is spun up which exposes the entire playwright API.
-You build a bunch of little actions to do much like action chains in Selenium, and then make 'em go whir.
+We ensure the node deps are installed in a BEGIN block, and then spin up the proxy server.
+You then use playwright more or less as normal; see the POD in Playwright.pm for more details.
 
 See example.pl for usage examples.
 

+ 0 - 1
bin/playwright.js

@@ -13,7 +13,6 @@ const fs = require('fs');
 let rawdata = fs.readFileSync('api.json');
 let spec = JSON.parse(rawdata);
 
-//TODO support device commands
 const argv = yargs
     .option('debug', {
         alias: 'd',

+ 2 - 0
lib/Playwright.pm

@@ -39,6 +39,8 @@ use feature qw{signatures state};
 =head1 DESCRIPTION
 
 Perl interface to a lightweight node.js webserver that proxies commands runnable by Playwright.
+Checks and automatically installs a copy of the node dependencies in the local folder if needed.
+
 Currently understands commands you can send to all the playwright classes defined in api.json.
 
 See L<https://playwright.dev/#version=master&path=docs%2Fapi.md&q=>