![]() ![]() 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 " # Update deps within packages (interactive) # Upgrade project wide deps like puppeteer # (We keep the devDependency version blurry) Yarn test # Update JSDoc based documentation in markdown files This can end up using a lot of extra space, at 92Mb per copy currently, on peoples drives. puppeteer-extra and all plugins are tested continously in a matrix of current (stable & LTS) NodeJS and puppeteer versions. Yarn lerna exec -concurrency 1 'yarn remove fs-extra echo 0 ' # Run test in all packages Problem As it is, every Puppeteer install will pull its own internal Chromium copy. 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. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |