sindresorhus/fullname

Get the fullname of the current user

fullname

Get the full name of the current user

Works on macOS, Linux, and Windows.

Install

npm install fullname

Usage

import fullName from 'fullname';

console.log(await fullName());
//=> 'Sindre Sorhus'

In the rare case a name cannot be found, you could fall back to username.

Related

• fullname-cli - CLI for this package
• fullname-native - Native version of this package
• username - Get the username of the current user

fullname's Issues

Refactor

The code is quite messy right now. Would be nice to use mem on the exported function instead of assigning to the global fullname in every step. Also separate each check into a top level function, so we can easily mix and match checks for each platform, and maybe even do some checks in parallel using Promise.race(). I don't have time to do this right now, but could be an interesting exercise for anyone looking to contribute. PR welcome :)

Add faster initial fallback check on OS X and Linux

Get the fullname using https://github.com/sindresorhus/passwd-user. Since it just reads the file from disk it should be a lot faster than the existing fallbacks.

Tried "fullname.sync()" like I normally did with username but error

c2runtime.js:16238 Error executing Javascript: ReferenceError: fullname is not defined

checkWmic function returns '\r\r\n\r' without user information

When I run individually from command prompt it gives a valid response.

C:\Users\Pradeep_Tippa>wmic useraccount where name="%username%" get fullname
FullName
Pradeep Kumar Tippa

Where as when i use checkWmic code it is failing.

C:\Users\Pradeep_Tippa>node sample.js
Stdout

We are using fullname().then(name) in our cli starter-app

Please help. Let me know if you need more information.

What is the script to fallback username when fullname isn't found?

@sindresorhus

Fall back to `git config` on Windows too

Fall back to 'git config --global user.name' on Windows too if the first one doesn't return anything.

Respect name changes

I am making first-name, which is built on top of this module.

Writing good tests for it is difficult because fullname caches the result. I could maybe use this trick but it seems ugly to do that to a dependency. And if I ever have to write a module on top of first-name where trying out different names is useful, then that modules's tests may not be able to do so because you can't always require a sub-dependency, depending on how npm structures the tree.

Any thoughts on approaches to deal with this?

More broadly, the memoization here is strange because fullname doesn't take any input. Thus it has no way to know when the computation should be performed again, which is a core tenet of memoization. And even though it may not be common, the user's name certainly can change.

My solutions:

1. fullname.noCache() does the same work, bypassing the cache.
2. fullname() implements a lazily updated cache. So it would have a shortcut to resolve quickly with a cached value if one is available, but would trigger a non-blocking background update of the cache so that future calls can return a more up-to-date value.
3. We leave everything as-is but use mem's cacheKey feature to cache based on relevant properties from process.env. So changes to the environment can be returned immediately. However, unlike 2, in the event that no environment variables are defined, the module keeps behaving as it does now (i.e. you are "stuck" with a name permanently).

My favorite is 3, and it would look something like this:

module.exports = mem(getFullName, {
    cacheKey(input) {
        return JSON.stringify(filterObj(process.env, [
            'GIT_AUTHOR_NAME',
            'GIT_COMMITTER_NAME'
            // ...
        ]));
    }
});

Get the fullname from `npmconf`

Using the npmconf module, get the init.author.name prop.

Should be faster than spawning a subprocess.

Run it concurrently with the subprocess in case it's not set.

Russian letters seem to cause the method to return object instead of a string

Hej,

sorry that this issue is kind of vague. @vitalkanev reported the issue in the yo repo over here: yeoman/yo#540.

I wasn’t able reproduce the issue with this username with Mac OS 10.12.6:

шуталы Phillipow

So it might be a linux specific issue?!?

npmconf is deprecated

Getting this WARN when installing this package:

$ npm i fullname
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm

Relies on vulnerable version of execa

As per the vulnerability report below, execa:1.0.0 has a critical vulnerability which has been fixed since version 2.0.0.
Would be great if you could do some package updates and related code changes.

Vulnerability report:
https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/execa/GMS-2020-2.yml

execa:2.0.0 release diff:
https://github.com/sindresorhus/execa/releases/tag/v2.0.0

The subprocess to get fullname not work in Ubuntu when user is a local user, but authenticated from Ldap

I suggest this fallback
grep "^whoami:" /etc/passwd | awk -F: '{print $5}'