Repository navigation
bug on create cloud #344
Description
Activity
Hi, thanks for the report. What is the
typeof config.get('google:cloud:id')? Is it not a string?Or how are you passing in the path to your key? The actual code snippet instead of a fake
path/to/google/key.jsonmight help us track down the issue.It looks like a dependency (user-home) of a dependency (xdg-basedir) of a dependency (configstore) of our library can't figure out your home directory: https://github.com/sindresorhus/user-home/blob/master/index.js
Is there any reason your system wouldn't be able to satisfy the search for a home directory here? https://github.com/sindresorhus/user-home/blob/master/index.js
If nothing else, it looks like setting the environment variable "HOME" with a path to your home directory will give Configstore a place to read and write files.
Configstore should handle that gracefully though: https://github.com/yeoman/configstore/blob/b82690fc401318ad18dcd7d151a0003a4898a314/index.js#L15
I think it's crashing before it gets to that point. https://github.com/sindresorhus/user-home/blob/master/index.js#L13 -- that must be returning undefined to https://github.com/sindresorhus/xdg-basedir/blob/master/index.js#L6
Fixed in sindresorhus/xdg-basedir@ec77240
It's really annoying we don't have a reliable way to get the home directory in Node... (libuv/libuv#11)
@sindresorhus thanks!
@leibale if you are still experiencing issues with gcloud, please re-open.
- addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
on Feb 2, 2015 - addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Apr 6, 2020 38 remaining items
- added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Feb 23, 2026 - added a commit that references this issue
on Feb 25, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 5, 2026 - added 2 commits that reference this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 18, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
and node throw this error:
in version 0.11.0 it's working
thanks