thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
547f4ea60a
puppeteer/.gitignore

19 lines
261 B
Plaintext
Raw Normal View History

Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
/node_modules/
test(firefox): introduce vendor-specific specs (#3890) Certain Puppeteer methods do expose the inner browser - e.g. `browser.version()` depends on the browser we run. Split out these tests into a vendor-specific test suites. References #3889
2019-02-02 01:55:12 +00:00
/test/output-chromium
/test/output-firefox
chore: Allow development under Windows platform (#992) This patch improves life of puppeteer contributor on Windows: - Setting environment variables using cross-env since Windows requires the SET command. - Calling Jasmine in the script debug-unit using jasmine's JavaScript binary instead of shell. - Add /test/test-user-data-dir* to .gitignore since temporary user data directories, in case of test fails, remains in the test directory.
2017-10-11 19:14:13 +00:00
/test/test-user-data-dir*
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
/.local-chromium/
(feat) Add option to fetch Firefox Nightly (#5467) * (feat) Add option to fetch Firefox Nightly Add Firefox support to BrowserFetcher and the install script. By default, the latest Firefox Nightly is downloaded directly from archive.mozilla.org (dmg, tar.bz2 and zip) This also required changes that impact `puppeteer.launch()` and `puppeteer.executablePath()` Fixes #5151 * Update docs/api.md Co-Authored-By: Mathias Bynens <mathias@qiwi.be> * Clean up revision promise * Improve error handling in revision check * Remove matchAll * Use explicit octal mode * Update .gitignore Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-03-10 20:59:03 +00:00
/.local-firefox/
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
/.dev_profile*
.DS_Store
*.swp
*.pyc
Intorduce Page.keyboard (#74) Introduce page.keyboard to provide low-level access to the keyboard.
2017-07-18 01:49:52 +00:00
.vscode
Ignore package-lock.json (#191) pacakge-lock.json seems to be buggy now, with different OS giving different results. See https://github.com/npm/npm/issues/17749 We have been having trouble keeping it up to date with yarn.lock. It doesn't give us a big win, because it is ignored if you install the package from npm. This patch removes package-lock.json and starts ignoring it.
2017-08-02 21:18:14 +00:00
package-lock.json
chore: switch to npm from yarn (#1878) This patch: - migrates CI to use NPM - drops lockfiles (`yarn.lock`). Lockfiles are ignored by package managers when the package is installed as a dependency, so this makes CI closer to the installation our clients run.
2018-01-23 01:11:10 +00:00
yarn.lock
Node 6 support (#484) This patch: - introduces a transpiler which substitutes async/await logic with generators. - starts using the transpiler to generate a node6-compatible version of puppeteer - introduces a runtime-check to decide which version of code to use Fixes #316.
2017-08-24 19:20:05 +00:00
/node6
chore: make sure Puppeteer bundling works (#3239) This patch: - adds "browser" field to the package.json with default bundling options. - introduces "bundle" and "unit-bundle" commands to create bundle and test bundle - starts running bundle tests on Travis Node 8 bots Fixes #2374.
2018-09-13 19:08:51 +00:00
/utils/browser/puppeteer-web.js
chore: move code to src/ and emit with TypeScript (#5568) This updates our `tsconfig.json` so it emits our JavaScript files as well as type checking them. We compile into `./lib` which we then ship in our npm package. The source code has moved from `./lib` into `./src`. Because the `src/` directory is exclusively JS files, this change is a no-op in terms of code functionality but is the first step towards being able to replace `src/X.js` with `src/X.ts` in a way that allows us to migrate incrementally. The `lib` directory is gitignored, and the `src` directory is npmignored. On `npm publish` we will now run `npm run tsc` in order to generate the outputted code.
2020-04-02 14:25:19 +00:00
/lib
chore: update how we track coverage during unit tests (#5779) * chore: update how we track coverage during unit tests The old method of tracking coverage was causing issues. If a test failed on CI, that test's failure would be lost because the test failing would in turn cause the coverage to fail, but the `process.exit(1)` in the coverage code caused Mocha to not output anything useful. Instead the coverage checker now: * tracks the coverage in memory in a Map (this hasn't changed) * after all tests, writes that to disk in test/coverage.json (which is gitignored) * we then run a single Mocha test that asserts every method was called. This means if the test run fails, the build will fail and give the error about that test run, and that output won't be lost when the coverage then fails too. Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-30 12:00:41 +00:00
test/coverage.json
chore: Introduce API Extractor and start generating documentation (#5967)
2020-06-04 10:47:13 +00:00
temp/
Reference in New Issue Copy Permalink