![]() ![]() PACKAGE=puppeteer-extra PACKAGE_DIR=/Users/foo/puppeteer-extra/packages & yarn remove $(echo $PACKAGE ) true & rm -f $(pwd )/ $(echo $PACKAGE )-latest.tgz & yarn -cwd $(echo $PACKAGE_DIR )/ $(echo $PACKAGE ) pack -filename $(pwd )/ $(echo $PACKAGE )-latest.tgz & YARN_CACHE_FOLDER=/tmp/yarn yarn add file: $(pwd )/ $(echo $PACKAGE )-latest. ![]() # Test a local monorepo package in an outside folder as it would've been installed from the registry # Change PACKAGE_DIR to the path of this monorepo and PACKAGE to the package you wish to install Yarn test # Run tests of specific stealth evasion cd packages/puppeteer-extra-plugin-stealth # Run tests of specific package cd packages/puppeteer-extra-plugin-stealth Rm -f yarn.lock & rm -rf node_modules & yarn cache clean Yarn lerna exec "rm -f yarn.lock rm -rf node_modules echo 0 " Usage Puppeteer will be familiar to people using other browser testing frameworks. ![]() Be sure that the version of puppeteer-core you install is compatible with the browser you intend to connect to. # Update deps within packages (interactive) puppeteer-core is intended to be a lightweight version of Puppeteer for launching an existing browser installation or for connecting to a remote one. # Upgrade project wide deps like puppeteer # (We keep the devDependency version blurry) The install will likely take a while as by default Puppeteer comes with its own copy of Chrome - this isn't required, as there is another package called puppeteer-core that you can use with your own browser instead, but I haven't tried this so won't go through it here. Yarn test # Update JSDoc based documentation in markdown files Yarn lerna exec -concurrency 1 'yarn remove fs-extra echo 0 ' # Run test in all packages Yarn lerna add fs-extra -scope=puppeteer-extra-plugin-user-data-dir # Install fs-extra to puppeteer-extra-plugin-user-data-dir ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |