@percy/core - npm Package Compare versions

dist/api.js

		import fs from 'fs';
		import path, { dirname, resolve } from 'path';
		import path from 'path';
		import { createRequire } from 'module';
		import logger from '@percy/logger';
		@@ -8,11 +9,4 @@ import { normalize } from '@percy/config/utils';
		import { handleSyncJob } from './snapshot.js';
		// Previously, we used `createRequire(import.meta.url).resolve` to resolve the path to the module.
		// This approach relied on `createRequire`, which is Node.js-specific and less compatible with modern ESM (ECMAScript Module) standards.
		// This was leading to hard coded paths when CLI is used as a dependency in another project.
		// Now, we use `fileURLToPath` and `path.resolve` to determine the absolute path in a way that's more aligned with ESM conventions.
		// This change ensures better compatibility and avoids relying on Node.js-specific APIs that might cause issues in ESM environments.
		import { fileURLToPath } from 'url';
		const __filename = fileURLToPath(import.meta.url);
		const __dirname = dirname(__filename);
		export const PERCY_DOM = resolve(__dirname, 'node_modules/@percy/dom');
		// need require.resolve until import.meta.resolve can be transpiled
		export const PERCY_DOM = createRequire(import.meta.url).resolve('@percy/dom');

		@@ -19,0 +13,0 @@ // Returns a URL encoded string of nested query params

package.json

dist/findRevision.sh

dist/timing.js

New alerts