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.

declare some third party variable like 'moment' in typing.d.ts, and run build library also throw: Cannot find name 'moment'

See original GitHub issue

Type of Issue

[ x] Bug Report
[ ] Feature Request

Description

declare some third party variable like ‘moment’ in typing.d.ts, and run build library also throw: Cannot find name ‘moment’

How To Reproduce

Expected Behaviour

how can i config this third party variable to build libary

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr:            5.3.0
@angular/compiler:     8.0.2
rollup:                1.16.2
tsickle:               0.35.0
typescript:            3.4.5

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:6 (2 by maintainers)

Top GitHub Comments

8reactions

raphael22commented, Sep 4, 2019

Welcome to my world of 1+ year of “nobody care”. https://github.com/ng-packagr/ng-packagr/issues/744

3reactions

raphael22commented, Sep 6, 2019

Hi, thanks for quick response.

It’s a matter of taking both benefit of peerDependencies and dependencies in a production context.

As an Angular deployed applications hub, I want to be able to import plugins angular applications. I don’t want them to copies peerDependencies, but I do want them to come with there own dependencies I don’t have already.

I want to be able to develop a new plugin application without having to reference it’s dependencies in my hub application and without to redeploy.

A nice final umd file which can be consume by another ALREADY built angular application. I can already achieve this with extra steps by installing dependencies in dist folder and using browserify on top on that but I guess it’s could be done by some rollup step on build.