@nestbridge/webpack 2.1.1 → 2.1.3

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.
package/CHANGELOG.md ADDED
@@ -0,0 +1,38 @@
1
+ # @nestbridge/webpack
2
+
3
+ ## 2.1.3
4
+
5
+ ### Patch Changes
6
+
7
+ - cec7886: Fix `Cannot find module '.../typescript/unstable/ast'` when loading `@nestbridge/vite` or `@nestbridge/webpack` in a project that has its own `typescript` (for example 6.x) installed. Each package previously bundled a private copy of its internal `@nestbridge/*` dependencies, so core's `typescript@7` import was resolved against the host project's `typescript` instead of the one core declares. Internal packages are now external, so imports resolve through the declared dependency chain and the bundles shrink accordingly.
8
+ - Updated dependencies [cec7886]
9
+ - @nestbridge/unplugin@2.1.3
10
+
11
+ ## 2.1.2
12
+
13
+ ### Patch Changes
14
+
15
+ - e391e8f: Fix `yarn add nestbridge` (and `npm install nestbridge`) failing with `Workspace not found (@nestbridge/runtime@workspace:*)`. Previously published manifests shipped Yarn's `workspace:*` dependency specifiers verbatim because the release pipeline packed with plain `npm publish`. Packages are now packed with `yarn pack`, which rewrites them to the real version, and the release aborts if any `workspace:` specifier survives in the tarball.
16
+ - Updated dependencies [e391e8f]
17
+ - @nestbridge/unplugin@2.1.2
18
+
19
+ ## 2.1.1
20
+
21
+ ### Patch Changes
22
+
23
+ - c7fe551: Fix `outputDir` resolving relative to `root` instead of the bundler's own project root. `root` now controls only where controllers, resolvers, and the bootstrap `main.ts` are discovered, while `outputDir` always resolves relative to Vite's `config.root` or webpack's `compiler.options.context`. This removes the need to widen `root` to a parent directory just to reach a bootstrap file that lives outside the client project, and fixes webpack builds that previously had no way to resolve their own project root at all.
24
+ - Updated dependencies [c7fe551]
25
+ - @nestbridge/unplugin@2.1.1
26
+
27
+ ## 2.1.0
28
+
29
+ ### Patch Changes
30
+
31
+ - Updated dependencies [a21adfa]
32
+ - @nestbridge/unplugin@2.1.0
33
+
34
+ ## 2.0.4
35
+
36
+ ### Patch Changes
37
+
38
+ - @nestbridge/unplugin@2.0.4
@@ -1,19 +1,10 @@
1
+ import { NestBridgeOptions, NestBridgeOptions as NestBridgeOptions$1 } from "@nestbridge/unplugin";
1
2
  import { WebpackPluginInstance } from "webpack";
2
- //#region ../unplugin/src/options/nestbridge-options.d.ts
3
- interface NestBridgeOptions {
4
- controllers: string | string[];
5
- resolvers?: string | string[];
6
- baseURL?: string;
7
- debug?: boolean;
8
- outputDir?: string;
9
- root?: string;
10
- }
11
- //#endregion
12
3
  //#region src/version.d.ts
13
4
  export declare const VERSION: string;
14
5
  //#endregion
15
6
  //#region src/main.d.ts
16
- export declare const nestBridge: (options: NestBridgeOptions) => WebpackPluginInstance;
7
+ export declare const nestBridge: (options: NestBridgeOptions$1) => WebpackPluginInstance;
17
8
  //#endregion
18
9
  export type { NestBridgeOptions };
19
10
  //# sourceMappingURL=nestbridge.webpack.d.ts.map