npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@freik/is-hidden-file

v1.13.1

Published

Check if a file/folder is hidden on node js that works on any platform.

Downloads

9

Readme

is-hidden-file

Latest Version on NPM here

Check if a file/folder is hidden on all platforms.

Forked from kimlimjustin/is-hidden-file to use CMake (reliable!) instead of node-gyp (inscrutably broken constantly for me), with other fixes (like an obvious memory leak)

Note This will slow down your yarn install/npm installs, particularly on Windows! The speed hit seems unavoidable. Package managers are terrible at understanding build dependencies, so they'll rebuild this whenever it gets installed, even if nothing changed. And the rebuild invokes some platform specific shim which is kind of slow. Once the shim is done, Linux and MacOS move merrily on their way. Windows, however, invokes the cmake build system, followed by the C++ compiler & linker, all of which is quite slow. The solution to this is to get the NodeJS runtime to add support for this to the path or fs modules... It's gotten bad enough that I'm digging for solutions like including pre-built x86 and AMD64 binaries in the NPM package...

  • On *nix: Check file name starts with ..
  • On Windows: Check if the file is hidden using native code.

Installation

  • npm: npm i is-hidden-file
  • yarn: yarn add is-hidden-file

Usage

It's packaged as both CJS and ESM: Use which module type your ecosystem requires. Typescript types are also included.

Node js with or without typescript

import { isHiddenFile } from 'is-hidden-file';
// Or this for CJS:
// const { isHiddenFile } = require('is-hidden-file');

console.log(isHiddenFile('.git')); // true
console.log(isHiddenFile('README.md')); // false

License

MIT, cuz that's what the original was licensed with.