Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bl@3.0.0 looks like an empty build. Contain only package.json #69

Closed
sagarvd01 opened this issue Aug 23, 2019 · 2 comments
Closed

bl@3.0.0 looks like an empty build. Contain only package.json #69

sagarvd01 opened this issue Aug 23, 2019 · 2 comments

Comments

@sagarvd01
Copy link

Hi team, it looks like bl@3.0.0 is an empty build. I had problems with firebase-tools and it looks like the issue is with bl. Downgrading bl to 2.2.0 worked.

You can see that issue here on firebase-tools repository

@rvagg
Copy link
Owner

rvagg commented Aug 24, 2019

I don't think this is a problem on our end, it's been out for 5 months without reported problems, and:

$ npm i bl@3.0.0
...
+ bl@3.0.0
added 6 packages from 2 contributors and audited 6 packages in 1.656s
found 0 vulnerabilities
$ cd node_modules/bl/
$ ls -al
total 40
drwxr-xr-x 9 rvagg wheel   288 Aug 24 13:53 .
drwxr-xr-x 8 rvagg wheel   256 Aug 24 13:53 ..
-rw-r--r-- 1 rvagg wheel  1167 Oct 26  1985 .jshintrc
-rw-r--r-- 1 rvagg wheel   169 Oct 26  1985 .travis.yml
-rw-r--r-- 1 rvagg wheel  1216 Oct 26  1985 LICENSE.md
-rw-r--r-- 1 rvagg wheel 11304 Oct 26  1985 README.md
-rw-r--r-- 1 rvagg wheel  9308 Oct 26  1985 bl.js
-rw-r--r-- 1 rvagg wheel  1631 Aug 24 13:53 package.json
drwxr-xr-x 4 rvagg wheel   128 Aug 24 13:53 test

@rvagg rvagg closed this as completed Aug 24, 2019
@sagarvd01
Copy link
Author

I don't know what is the problem here. I installed bl manually on firebase-tools installation folder and still it showed only package.json (as mentioned in the issue in firebase-tools repo. After downgrading to bl@2.2.0, the problem is fixed and I'm using firebase cli now without any problem. Just now I noticed that last publish of bl happened 6 months ago. So this may be an issue with a cache server of npm or something I don't know.

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

No branches or pull requests

2 participants