@atlaspack/package-manager 2.14.5-dev.93 → 2.14.5-dev.97

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/lib/NodePackageManager.js +7 -6
  2. package/package.json +10 -10
  3. package/src/NodePackageManager.js +7 -6
package/lib/NodePackageManager.js CHANGED
@@ -105,7 +105,7 @@ function _interopRequireWildcard(e, r) { if (!r && e && e.__esModule) return e;
105
105
  // Package.json fields. Must match package_json.rs.
106
106
  const MAIN = 1 << 0;
107
107
  const SOURCE = 1 << 2;
108
- const ENTRIES = process.env.ATLASPACK_REGISTER_USE_LIB === 'true' ? MAIN : MAIN | (process.env.ATLASPACK_BUILD_ENV !== 'production' || process.env.ATLASPACK_SELF_BUILD ? SOURCE : 0);
108
+ const ENTRIES = process.env.ATLASPACK_REGISTER_USE_LIB === 'true' ? MAIN : MAIN | (process.env.ATLASPACK_BUILD_ENV === 'test' || process.env.ATLASPACK_SELF_BUILD ? SOURCE : 0);
109
109
  const NODE_MODULES = `${_path().default.sep}node_modules${_path().default.sep}`;
110
110
 
111
111
  // There can be more than one instance of NodePackageManager, but node has only a single module cache.
@@ -500,11 +500,12 @@ class NodePackageManager {
500
500
  return;
501
501
  }
502
502
 
503
- // During testing don't invalidate Atlaspack modules because
504
- // this causes failures due to multiple instances of the same module
505
- // existing simultaniously. This is fine when using babel-register because
506
- // it has an internal module cache that NodePacakageManager does not invalidate
507
- // but fails when using compiled Atlaspack packages in integration tests
503
+ // Skip invalidation of Atlaspack modules during testing to prevent
504
+ // module cache conflicts. When using babel-register, this works fine
505
+ // because it maintains its own internal module cache that we don't
506
+ // invalidate. However, with compiled Atlaspack packages in integration
507
+ // tests, invalidation causes multiple module instances to exist
508
+ // simultaneously, leading to test failures.
508
509
  if (process.env.ATLASPACK_BUILD_ENV === 'test' && name.startsWith('@atlaspack/')) {
509
510
  return;
510
511
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@atlaspack/package-manager",
3
- "version": "2.14.5-dev.93+207d003c0",
3
+ "version": "2.14.5-dev.97+70270d69e",
4
4
  "description": "Blazing fast, zero configuration web application bundler",
5
5
  "license": "(MIT OR Apache-2.0)",
6
6
  "publishConfig": {
@@ -39,14 +39,14 @@
39
39
  }
40
40
  },
41
41
  "dependencies": {
42
- "@atlaspack/build-cache": "2.13.3-dev.161+207d003c0",
43
- "@atlaspack/diagnostic": "2.14.1-dev.161+207d003c0",
44
- "@atlaspack/fs": "2.14.5-dev.93+207d003c0",
45
- "@atlaspack/logger": "2.14.5-dev.93+207d003c0",
46
- "@atlaspack/node-resolver-core": "3.5.5-dev.93+207d003c0",
47
- "@atlaspack/types": "2.14.5-dev.93+207d003c0",
48
- "@atlaspack/utils": "2.14.5-dev.93+207d003c0",
49
- "@atlaspack/workers": "2.14.5-dev.93+207d003c0",
42
+ "@atlaspack/build-cache": "2.13.3-dev.165+70270d69e",
43
+ "@atlaspack/diagnostic": "2.14.1-dev.165+70270d69e",
44
+ "@atlaspack/fs": "2.14.5-dev.97+70270d69e",
45
+ "@atlaspack/logger": "2.14.5-dev.97+70270d69e",
46
+ "@atlaspack/node-resolver-core": "3.5.5-dev.97+70270d69e",
47
+ "@atlaspack/types": "2.14.5-dev.97+70270d69e",
48
+ "@atlaspack/utils": "2.14.5-dev.97+70270d69e",
49
+ "@atlaspack/workers": "2.14.5-dev.97+70270d69e",
50
50
  "@swc/core": "^1.10.0",
51
51
  "semver": "^7.5.2"
52
52
  },
@@ -63,5 +63,5 @@
63
63
  "./src/Yarn.js": false
64
64
  },
65
65
  "type": "commonjs",
66
- "gitHead": "207d003c0f1d4ffa6a1c52d2f8841d998616c523"
66
+ "gitHead": "70270d69e3144a59f39970e1bcaa61c779342b11"
67
67
  }
package/src/NodePackageManager.js CHANGED
@@ -45,7 +45,7 @@ const ENTRIES =
45
45
  process.env.ATLASPACK_REGISTER_USE_LIB === 'true'
46
46
  ? MAIN
47
47
  : MAIN |
48
- (process.env.ATLASPACK_BUILD_ENV !== 'production' ||
48
+ (process.env.ATLASPACK_BUILD_ENV === 'test' ||
49
49
  process.env.ATLASPACK_SELF_BUILD
50
50
  ? SOURCE
51
51
  : 0);
@@ -557,11 +557,12 @@ export class NodePackageManager implements PackageManager {
557
557
  return;
558
558
  }
559
559
 
560
- // During testing don't invalidate Atlaspack modules because
561
- // this causes failures due to multiple instances of the same module
562
- // existing simultaniously. This is fine when using babel-register because
563
- // it has an internal module cache that NodePacakageManager does not invalidate
564
- // but fails when using compiled Atlaspack packages in integration tests
560
+ // Skip invalidation of Atlaspack modules during testing to prevent
561
+ // module cache conflicts. When using babel-register, this works fine
562
+ // because it maintains its own internal module cache that we don't
563
+ // invalidate. However, with compiled Atlaspack packages in integration
564
+ // tests, invalidation causes multiple module instances to exist
565
+ // simultaneously, leading to test failures.
565
566
  if (
566
567
  process.env.ATLASPACK_BUILD_ENV === 'test' &&
567
568
  name.startsWith('@atlaspack/')