Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Release 1.2.0 throws compiler error with typescript < 2.0.0

See original GitHub issue

Since the 1.2.0 release is built with typescript 2.0.0 the file scroller.d.ts containes the reference to @types typings which don’t work with the current stable release of typescript (1.8.x) and throw a compiler error.

Issue Analytics

State:
Created 7 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

zoehnetocommented, Aug 28, 2016

PR #73 should work for both TypeScript 1.8 and 2.0 by replacing the core-js dependency with the built-in typings for compilation, allowing everyone to use their preferred polyfill at runtime (or skipping it completely).

0reactions

orizenscommented, Aug 28, 2016

thanks

Top Results From Across the Web

Package "@angular/compiler-cli" has an incompatible peer ...

I found through trial and error that I had to use a specific version of typescript which is 3.1.6. Here's what I did....

Angular upgrade from version 8 to 15. Error "Cannot use ...

I am trying to update angular app from 8 to 15 after updating all the packages, app is throwing below error ...

Documentation - TypeScript 2.0

A property access or a function call produces a compile-time error if the object or function is of a type that includes null...

package.json - npm Docs

In npm versions 3 through 6, peerDependencies were not automatically installed, and would raise a warning if an invalid version of the peer...

Bug listing with status RESOLVED with resolution OBSOLETE ...

... Bug:5012 - "ALSA ebuild error" status:RESOLVED resolution:OBSOLETE severity:normal ... Bug:312089 - "=dev-vcs/cssc-1.2.0 does not compile on *-macos" ...