Skip to content
This repository has been archived by the owner on Jun 25, 2024. It is now read-only.

Use bower postinstall after running npm install, why? #78

Open
danfergo opened this issue Jan 18, 2018 · 7 comments
Open

Use bower postinstall after running npm install, why? #78

danfergo opened this issue Jan 18, 2018 · 7 comments

Comments

@danfergo
Copy link

I'm trying to install pdfjs-viewer with npm and avoid bower, but the package.json postinstall requires bower.

@aemc
Copy link

aemc commented Jan 31, 2018

yea it doesn't make any sense

danfergo added a commit to danfergo/angular-pdfjs-viewer that referenced this issue Feb 6, 2018
@tiagomsmagalhaes
Copy link

having this issue and ESUDO error because of running as root

@tiagomsmagalhaes
Copy link

thanks @danfergo. You could pull a PR

is having issues with bower change your package.jsonentry for this package to

"angular-pdfjs-viewer": "danfergo/angular-pdfjs-viewer#patch-1"

while this isn't patched

@jasny
Copy link
Member

jasny commented May 18, 2018

Package dependencies are managed in bower, but we'll add those to package.json instead

@jasny
Copy link
Member

jasny commented May 18, 2018

I've requested to gain control of the pdf.js-viewer from @lostip via Twitter.

https://twitter.com/ArnoldDaniels/status/997524041249558534

@adhityan
Copy link

@jasny Any update on this? I see you got access to pdf.js-viewer from @lostip

@adnan-oodles
Copy link

adnan-oodles commented Aug 14, 2019

Any update on this or do I still need to use the patched version mentioned by @tiagomsmagalhaes above?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants