graceful-fs
chokidar
graceful-fs | chokidar | |
---|---|---|
3 | 27 | |
1,272 | 11,007 | |
- | - | |
3.0 | 8.7 | |
4 months ago | 9 days ago | |
JavaScript | JavaScript | |
ISC License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
graceful-fs
-
My fist codestory. A day in my life, as a coder :)
async (config?: { /** * Overwrite the default ignored behavior */ customIgnored?: string[]; }) => { const projectRoot = getProjectRoot(); if (!projectRoot) return; // NB: fix to globally alter real fs in order to fix EMFile error that happens in TSMorph (see https://github.com/isaacs/node-graceful-fs) gracefulFs.gracefulify(realFs); console.log("Searching..."); const tsFunctions = await db.get("TsFunction"); const projectWatcherTsFunctions = tsFunctions.filter( (x) => x.explicitTypeName === "ProjectWatcher" ); const projectWatchers = projectWatcherTsFunctions .map((x) => x.name) .map((name) => sdk[name as keyof typeof sdk] as ProjectWatcher | undefined) .filter(notEmpty); log(`${projectWatchers.length} watchers gonna watch ${projectRoot}`, { type: "important", }); const startupWaitMs = 1000; setTimeout(() => { log( `There they are! \n\n${projectWatchers .map((projectWatcher) => { return `π π ${projectWatcher.name} β `; }) .join("\n")}`, { type: "success", } ); }, startupWaitMs); const startTimeAt = Date.now(); watch(projectRoot, { ignoreInitial: true, ignored: config?.customIgnored || [ "**/node_modules/**", "**/.next/**", "**/.expo/**", "**/build/**", "**/db/**", "**/.git/**", "**/.turbo/**", "**/generated/**", ], // alwaysStat: true, // not sure why I would need this, seems inefficient if I don't need it, I can simply run fs.stat }).on("all", (eventName, path, stats) => { if (Date.now() < startTimeAt + startupWaitMs) return; const relevantWatchers = projectWatchers.filter((watcher) => watcher.filter(eventName, path) ); oneByOne(relevantWatchers, async (projectWatcher) => { await projectWatcher(eventName, path); }); }); };
-
My theory on why so many people are bad at coding.
What's probably got your shorts in a knot is the contents of the node_modules directory. That directory is a cache for mode.js modules so the tutorial can function standalone without having to install anything else. Treat it as you would object code. I pulled a half-dozen of those modules at random and went to their repositories. Every one of them had unit tests: block-stream, graceful-fs, lowercase-keys, minimist, pify and safe-buffer. Nobody sane ships unit tests with their executables.
-
I'm a noob, I've hit a wall and I need a bit of handholding re: creating node.js app
graceful-fs https://www.npmjs.com/package/graceful-fs
chokidar
-
Migrating from chokidar 3.x to 4.x
A big win recently in the e18e space is that chokidar published a new 4.x version!
- Chokidar 4.0
-
Boosting Rocket.Chat App Development with Hot Reload
I used the Chokidar library to watch for changes in the project directory. Chokidar detects file changes and triggers deployment commands automatically.
-
How to build a Web IDE like codesandbox?
We have a file explorer and a terminal, since files or directories could also be modified via terminal we need a way to communicate those changes to frontend. For this I made use of Chokidar, this package lets us setup file system watcher (nodemon also makes use of chokidar) and through following callbacks we can communicate file system changes.
-
The best testing setup for frontends, with Playwright and NextJS
For this, we'll use chokidar - more specifically the chokidar-cli package. chokidar is probably the most useful file watching library for the nodejs ecosystem and it will serve us well.
-
Why Does 'Is-Number' Package Have 59M Weekly Downloads?
tailwindcss -> chokidar -> braces -> fill-range -> to-regex-range -> is-number
is-number was first published 9 years ago, when these kind of micro-packages were in vogue. braces was added as a dependency to chokidar over 6 years ago [1]. And if it ain't broke, don't fix it. I don't think the average JS dev today is going out and pulling in these deps.
[1] https://github.com/paulmillr/chokidar/commit/cbdf25563cfff7f...
-
How nodemon works?
The watching magic is really in the https://www.npmjs.com/package/chokidar library
-
Dart 3.1 and a retrospective on functional style programming in Dart
> Itβs typical to listen to this stream of events and use chained if-else statements to determine an action based on the type of the events that occur.
You'd think something like directory watching would have a clear set of events that would make nice objects with consistent meanings, but in my experience file watching gets crazy complicated, and can have all sorts of edge cases.
Just take a looked here for all the various edge cases that crop up: https://github.com/paulmillr/chokidar/issues
Then you have linux, windows, macos, and maybe you want to abstract over some underlying implementation like chokidar vs fb/watchman vs webpack/watchpack. Every new OS release could also cause things to change.
So usually its going to be a bunch of if-else statements hacked together to get around edge cases, and have to be revisited later on.
Any attempt to abstract this into objects, just obfuscates things. And OO forces you to name things, when in fact they might be un-nameable. `FileSystemModifyEventExceptWhenXAndYAndSometimesZ`.
The behavior might rely on a series of events together, so the object hierarchy must be re-worked.
OO has this rosy idea that we just have to come up with the perfect hierarchy, but things change in unexpected ways, and everything must have a descriptive noun.
-
Is there anyway to auto reload the browser page when using express?
Next, you can use a library like chokidar to listen for changes in your source directory. Create a ws server, and whenever a file changes, send a message.
-
How does nodemon works under the hood?
As another has mentioned, nodemon uses chokidar under the hood for the actual file watching part.
What are some alternatives?
fs-extra - Node.js: extra methods for the fs object like copy(), remove(), mkdirs()
Filehound - Flexible and fluent interface for searching the file system
fs-jetpack - Better file system API for Node.js
Nodemon.io - Monitor for any changes in your node.js application and automatically restart the server - perfect for development
globby - User-friendly glob matching
proper-lockfile - An inter-process and inter-machine lockfile utility that works on a local or network file system.
Watch-fn
fs-write-stream-atomic - Like `fs.createWriteStream(...)`, but atomic.
mkdirp - Recursively mkdir, like `mkdir -p`, but in node.js
filenamify - Convert a string to a valid safe filename