This PR contains the following updates:

Release Notes

<details> <summary>typescript-eslint/typescript-eslint</summary>

v4.0.1

Compare Source

Bug Fixes

• eslint-plugin: update parser dependency range (#​2445) (2cb6620), closes #​2444

v4.0.0

Compare Source

Bug Fixes

• eslint-plugin: [no-shadow] fix false-positive on enum declaration (#​2374) (9de669f)
• eslint-plugin: [no-unused-vars] handle TSCallSignature (#​2336) (c70f54f)
• correct decorator traversal for AssignmentPattern (#​2375) (d738fa4)
• scope-manager: correct analysis of abstract class properties (#​2420) (cd84549)
• typescript-estree: correct ChainExpression interaction with parentheses and non-nulls (#​2380) (762bc99)

Features

• consume new scope analysis package (#​2039) (3be125d)
• support ESTree optional chaining representation (#​2308) (e9d2ab6)
• eslint-plugin: [ban-ts-comment] change default for ts-expect-error to allow-with-description (#​2351) (a3f163a), closes #​2146
• eslint-plugin: [no-unnecessary-condition][strict-boolean-expressions] add option to make the rules error on files without strictNullChecks turned on (#​2345) (9273441)
• eslint-plugin: [typedef] remove all defaults (#​2352) (a9cd6fb)
• eslint-plugin: add consistent-type-imports rule (#​2367) (58b1c2d)
• typescript-estree: switch to globby (#​2418) (3a7ec9b), closes #​2398

BREAKING CHANGES

• typescript-estree: - removes the ability to supply a RegExp to projectFolderIgnoreList, and changes the meaning of the string value from a regex to a glob.

• • Removed decorators property from several Nodes that could never semantically have them (FunctionDeclaration, TSEnumDeclaration, and TSInterfaceDeclaration)

• Removed AST_NODE_TYPES.Import. This is a minor breaking change as the node type that used this was removed ages ago.

• eslint-plugin: Default rule options is a breaking change.

3.10.1 (2020-08-25)

Bug Fixes

• eslint-plugin: [no-unnecessary-condition] correct regression with unary negations (#​2422) (d1f0887), closes #​2421

</details>

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about these updates again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

This PR contains the following updates:

Release Notes

<details> <summary>Microsoft/TypeScript</summary>

v4.0.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v4.0.0 (Beta).
• fixed issues query for Typescript v4.0.1 (RC).
• fixed issues query for Typescript v4.0.2.

Downloads are available on:

• npm
• Visual Studio 2017/2019 (Select new version in project options)
• NuGet package

</details>

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

Current package.json:

  "peerDependencies": {
    "react": "^16.3.2",
    "react-dom": "^16.3.2"
  },

I'm not sure, but seems to work fine with React v15. What specifically is required from React v16? If nothing, could I please make a "suggested enhancement":

  "peerDependencies": {
    "react": ">=15",
    "react-dom": ">=15"
  },

If it does require v16, it would be great if you could add a quick note in the README about why.

On the surface it works well, but if the observing node changes you'll run into a bug: https://github.com/researchgate/react-intersection-observer/blob/master/src/IntersectionObserver.ts#L109. That's one of the a reasons why React 15 is no longer supported, because it made logic like this extremely and unnecessarily complex.

We can add sideEffects: false to package.json so that tools like webpack effectively do tree-shaking. I'll see what I can do. In any case, can you create an example with codesandbox.io to see why hooks didn't work for your case?

Could you create a minimal example in codesanbox.io?

Thanks for filing an issue anyway, glad it got resolved. We didn't realize because we run a nexus proxy in front of NPM.

@saitonakamura would you happen to have time to have a look?

:tada: This PR is included in version 1.3.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

This PR contains the following updates:

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

Description

Now files in this directories are under src folder Not sure if it's supposed to or it's an overlook Anyway it's better to fix this quick

Motivation and context

Fixes #150

How has this been tested?

yarn test && yarn lint

Type of change

<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

<!--- Go over all the following points, and put an x in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->

• [ ] My code follows the code style of this project
• [ ] My change requires a change to the documentation
• [ ] I have updated the documentation accordingly
• [x] I have read the CONTRIBUTING document
• [ ] I have added tests to cover my changes
• [x] All new and existing tests passed

Expected behavior

No TypeScript errors.

Current behavior

TypeScript outputs the error:

Cannot find module '@researchgate/react-intersection-observer' or its corresponding type declarations.ts(2307)

Steps to reproduce

See https://codesandbox.io/s/nostalgic-shadow-qz6gh?file=/src/App.tsx

Context (environment)

• Version: 1.3.0
• Platform: Darwin F200420NT01.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64