- Consolidated duplicate UndoManagers to single instance - Fixed connection promise to only resolve on 'connected' status - Fixed WebSocketProvider import (WebsocketProvider) - Added proper doc.destroy() cleanup - Renamed isPresenceInitialized property to avoid conflict Co-Authored-By: Paperclip <noreply@paperclip.ing>
165 lines
4.5 KiB
Plaintext
165 lines
4.5 KiB
Plaintext
/**
|
|
* Copyright (c) Meta Platforms, Inc. and affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @flow strict-local
|
|
* @format
|
|
*/
|
|
|
|
import type {FSWatcher} from 'fs';
|
|
|
|
import {AbstractWatcher} from './AbstractWatcher';
|
|
import {includedByGlob, typeFromStat} from './common';
|
|
import {promises as fsPromises, watch} from 'fs';
|
|
import {platform} from 'os';
|
|
import * as path from 'path';
|
|
|
|
// eslint-disable-next-line import/no-commonjs
|
|
const debug = require('debug')('Metro:NativeWatcher');
|
|
|
|
const TOUCH_EVENT = 'touch';
|
|
const DELETE_EVENT = 'delete';
|
|
const RECRAWL_EVENT = 'recrawl';
|
|
|
|
/**
|
|
* NativeWatcher uses Node's native fs.watch API with recursive: true.
|
|
*
|
|
* Supported on macOS (and potentially Windows), because both natively have a
|
|
* concept of recurisve watching, via FSEvents and ReadDirectoryChangesW
|
|
* respectively. Notably Linux lacks this capability at the OS level.
|
|
*
|
|
* Node.js has at times supported the `recursive` option to fs.watch on Linux
|
|
* by walking the directory tree and creating a watcher on each directory, but
|
|
* this fits poorly with the synchronous `watch` API - either it must block for
|
|
* arbitrarily large IO, or it may drop changes after `watch` returns. See:
|
|
* https://github.com/nodejs/node/issues/48437
|
|
*
|
|
* Therefore, we retain a fallback to our own application-level recursive
|
|
* FallbackWatcher for Linux, which has async `startWatching`.
|
|
*
|
|
* On Windows, this watcher could be used in principle, but needs work around
|
|
* some Windows-specific edge cases handled in FallbackWatcher, like
|
|
* deduping file change events, ignoring directory changes, and handling EPERM.
|
|
*/
|
|
export default class NativeWatcher extends AbstractWatcher {
|
|
#fsWatcher: ?FSWatcher;
|
|
|
|
static isSupported(): boolean {
|
|
return platform() === 'darwin';
|
|
}
|
|
|
|
constructor(
|
|
dir: string,
|
|
opts: Readonly<{
|
|
ignored: ?RegExp,
|
|
globs: ReadonlyArray<string>,
|
|
dot: boolean,
|
|
...
|
|
}>,
|
|
) {
|
|
if (!NativeWatcher.isSupported) {
|
|
throw new Error('This watcher can only be used on macOS');
|
|
}
|
|
super(dir, opts);
|
|
}
|
|
|
|
async startWatching(): Promise<void> {
|
|
this.#fsWatcher = watch(
|
|
this.root,
|
|
{
|
|
// Don't hold the process open if we forget to close()
|
|
persistent: false,
|
|
// FSEvents or ReadDirectoryChangesW should mean this is cheap and
|
|
// ~instant on macOS or Windows.
|
|
recursive: true,
|
|
},
|
|
(event, relativePath) => {
|
|
this._handleEvent(event, relativePath).catch(error => {
|
|
this.emitError(error);
|
|
});
|
|
},
|
|
);
|
|
|
|
debug('Watching %s', this.root);
|
|
}
|
|
|
|
/**
|
|
* End watching.
|
|
*/
|
|
async stopWatching(): Promise<void> {
|
|
await super.stopWatching();
|
|
if (this.#fsWatcher) {
|
|
this.#fsWatcher.close();
|
|
}
|
|
}
|
|
|
|
async _handleEvent(event: string, relativePath: string) {
|
|
const absolutePath = path.resolve(this.root, relativePath);
|
|
if (this.doIgnore(relativePath)) {
|
|
debug(
|
|
'Ignoring event "%s" on %s (root: %s)',
|
|
event,
|
|
relativePath,
|
|
this.root,
|
|
);
|
|
return;
|
|
}
|
|
debug(
|
|
'Handling event "%s" on %s (root: %s)',
|
|
event,
|
|
relativePath,
|
|
this.root,
|
|
);
|
|
|
|
try {
|
|
const stat = await fsPromises.lstat(absolutePath);
|
|
const type = typeFromStat(stat);
|
|
|
|
// Ignore files of an unrecognized type
|
|
if (!type) {
|
|
return;
|
|
}
|
|
|
|
if (!includedByGlob(type, this.globs, this.dot, relativePath)) {
|
|
return;
|
|
}
|
|
|
|
// For directory "rename" events, notify that we need a recrawl since we
|
|
// wont' receive events for unmodified files underneath a moved (or
|
|
// cloned) directory. Renames are fired by the OS on moves, clones, and
|
|
// creations. We ignore "change" events because they indiciate a change
|
|
// to directory metadata, rather than its path or existence.
|
|
if (type === 'd' && event === 'rename') {
|
|
debug(
|
|
'Directory rename detected on %s, requesting recrawl',
|
|
relativePath,
|
|
);
|
|
this.emitFileEvent({
|
|
event: RECRAWL_EVENT,
|
|
relativePath,
|
|
});
|
|
return;
|
|
}
|
|
|
|
this.emitFileEvent({
|
|
event: TOUCH_EVENT,
|
|
relativePath,
|
|
metadata: {
|
|
type,
|
|
modifiedTime: stat.mtime.getTime(),
|
|
size: stat.size,
|
|
},
|
|
});
|
|
} catch (error) {
|
|
if (error?.code !== 'ENOENT') {
|
|
this.emitError(error);
|
|
return;
|
|
}
|
|
|
|
this.emitFileEvent({event: DELETE_EVENT, relativePath});
|
|
}
|
|
}
|
|
}
|