GithubHelp home page GithubHelp logo

stevenvachon / is-dom-detached Goto Github PK

View Code? Open in Web Editor NEW
2.0 1.0 0.0 201 KB

Determine if a Node does not exist within a DOM tree.

License: MIT License

JavaScript 100.00%
dom orphan node element stray

is-dom-detached's Introduction

is-dom-detached NPM Version File Size Build Status Coverage Status Dependency Monitor

Determine if a Node does not exist within a DOM tree.

Installation

Node.js >= 10 is required. To install, type this at the command line:

npm install is-dom-detached

Importing

ES Module:

import isDetachedNode from 'is-dom-detached';

CommonJS Module:

const isDetachedNode = require('is-dom-detached');

Usage

const div = document.createElement('div');
isDetachedNode(div); //-> true

document.body.appendChild(div);
isDetachedNode(div); //-> false

is-dom-detached's People

Contributors

stevenvachon avatar

Stargazers

 avatar

Watchers

 avatar

is-dom-detached's Issues

An in-range update of rimraf is breaking the build 🚨

The devDependency rimraf was updated from 2.6.3 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 250ee15 2.7.0
  • dc1682d feat: make it possible to omit glob dependency

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of coveralls is breaking the build 🚨

The devDependency coveralls was updated from 3.0.5 to 3.0.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • coverage/coveralls: First build on greenkeeper/coveralls-3.0.6 at 87.5% (Details).

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/cli was updated from 7.6.2 to 7.6.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

    • The devDependency @babel/cli was updated from 7.6.4 to 7.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of puppeteer is breaking the build 🚨

The devDependency puppeteer was updated from 1.17.0 to 1.18.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v1.18.0

Big Changes

  • Chromium 77.0.3827.0 (r669486)

API changes

No API changes.

Bug Fixes

  • #2755 - blurry canvas if deviceScaleFactor > 1
  • #4442 - Some pages not fully loading when setRequestInterception set to true
  • #4449 - goto takes an increasing amount of time.
  • #4454 - Intercepted requests won't return with some status codes
  • #4536 - Dangling promises / unhandled rejection due to missing await keywords in mouse.click
  • #4537 - Page.select throwing error when select change page
  • #4543 - Cannot retrieve content of pages that are >100MB.
  • #4545 - page.queryObjects doesn't work as expected
  • #4556 - https-agent makes http PUPPETEER_DOWNLOAD_HOST download fail
  • #4559 - non matching contribution rules makes PR have errors
  • #4563 - Too large write data is pending: size=725124416, max_buffer_size=268435456
  • #4568 - A3 paper size is incorrect

Raw notes

45873ea - feat(chromium): roll Chromium to r669486 (#4591)
955e7cb - feat(page): move page.pdf to protocol streams (#4587)
6c2007f - docs(README.md): fix spelling of Stack Overflow (#4590)
62733a2 - fix(connection): bump websocket max received message size to 256Mb (#4571)
5087962 - feat(chromium): roll Chromium to r668716 (#4581)
6860d73 - fix(network): align HTTP status codes with IANA (#4567)
7922641 - fix(page): fix A2 and A3 format size (#4569)
65b7e8e - docs(api.md): add notes on race condition in page.setViewport (#4319)
8df0b3e - fix(network): allow fulfilling requests with status code 422 (#4566)
b2f9490 - fix(eval): be able to throw protocol like errors (#4551)
6a50888 - fix(firefox): fix missing awaits in mouse.click (#4561)
e1432cc - docs(contributing): update commit message example (#4560)
dd6fcfe - fix(page): fix missing awaits in mouse.click (#4541)
7faf1c9 - fix(BrowserFetcher): fix httpRequest when using proxy against http HOST (#4558)
4bcdfc9 - docs(api.md): clarify frame/page.goto()'s handling of HTTP error statuses (#4553)
aca99cd - docs(troubleshooting): add missing double quotes (#4548)
90df69c - fix(page): do evaluations with one roundtrip (#4539)
7e19846 - feat(chromium): roll Chromium to r666595 (#4530)
f79d0a3 - fix: try running without --disable-gpu on windows (#4523)
15804d1 - test: remove debug console.log (#4522)
78d5106 - feat(chromium): roll Chromium to r665405 (#4516)
f52738e - docs(api.md): clarify on HTTP error responses (#4507)
94ff4de - docs(troubleshooting): fix comment (#4512)
ac611ba - fix(helper): fix Helper.installAsyncStackHooks method (#4478)
d221c02 - test: add test to verify fetching of dataURL requests (#4233)
015e330 - test: add oopif tests (#4495)
111350c - docs(troubleshooting.md): update Alpine instructions (#4494)
084cf02 - chore: bump version to v1.17.0-post (#4468)

Commits

The new version differs by 29 commits.

  • c96454d chore: mark version v1.18.0 (#4606)
  • 45873ea feat(chromium): roll Chromium to r669486 (#4591)
  • 955e7cb feat(page): move page.pdf to protocol streams (#4587)
  • 6c2007f docs(README.md): fix spelling of Stack Overflow (#4590)
  • 62733a2 fix(connection): bump websocket max received message size to 256Mb (#4571)
  • 5087962 feat(chromium): roll Chromium to r668716 (#4581)
  • 6860d73 fix(network): align HTTP status codes with IANA (#4567)
  • 7922641 fix(page): fix A2 and A3 format size (#4569)
  • 65b7e8e docs(api.md): add notes on race condition in page.setViewport (#4319)
  • 8df0b3e fix(network): allow fulfilling requests with status code 422 (#4566)
  • b2f9490 fix(eval): be able to throw protocol like errors (#4551)
  • 6a50888 fix(firefox): fix missing awaits in mouse.click (#4561)
  • e1432cc docs(contributing): update commit message example (#4560)
  • dd6fcfe fix(page): fix missing awaits in mouse.click (#4541)
  • 7faf1c9 fix(BrowserFetcher): fix httpRequest when using proxy against http HOST (#4558)

There are 29 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.