@nestjs/cli 11.0.12 → 11.0.14

package/actions/start.action.js

@@ -108,10 +108,15 @@ class StartAction extends build_action_1.BuildAction {
             processArgs.unshift(envFileNodeArgs.join(' '));
         }
         processArgs.unshift('--enable-source-maps');
-        return (0, child_process_1.spawn)(binaryToRun, processArgs, {
+        const spawnOptions = {
             stdio: 'inherit',
             shell: options.shell,
-        });
+        };
+        if (options.shell) {
+            const command = [binaryToRun, ...processArgs].join(' ');
+            return (0, child_process_1.spawn)(command, spawnOptions);
+        }
+        return (0, child_process_1.spawn)(binaryToRun, processArgs, spawnOptions);
     }
 }
 exports.StartAction = StartAction;

package/lib/runners/abstract.runner.js

@@ -19,7 +19,8 @@ class AbstractRunner {
             shell: true,
         };
         return new Promise((resolve, reject) => {
-            const child = (0, child_process_1.spawn)(`${this.binary}`, [...this.args, ...args], options);
+            const command = [this.binary, ...this.args, ...args].join(' ');
+            const child = (0, child_process_1.spawn)(command, options);
             if (collect) {
                 child.stdout.on('data', (data) => resolve(data.toString().replace(/\r\n|\n/, '')));
             }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nestjs/cli",
-  "version": "11.0.12",
+  "version": "11.0.14",
   "description": "Nest - modern, fast, powerful node.js web framework (@cli)",
   "publishConfig": {
     "access": "public"
@@ -48,27 +48,27 @@
     "cli-table3": "0.6.5",
     "commander": "4.1.1",
     "fork-ts-checker-webpack-plugin": "9.1.0",
-    "glob": "12.0.0",
+    "glob": "13.0.0",
     "node-emoji": "1.11.0",
     "ora": "5.4.1",
     "tsconfig-paths": "4.2.0",
     "tsconfig-paths-webpack-plugin": "4.2.0",
     "typescript": "5.9.3",
-    "webpack": "5.100.2",
+    "webpack": "5.103.0",
     "webpack-node-externals": "3.0.0"
   },
   "devDependencies": {
     "@commitlint/cli": "20.1.0",
     "@commitlint/config-angular": "20.0.0",
     "@swc/cli": "0.7.9",
-    "@swc/core": "1.15.2",
+    "@swc/core": "1.15.3",
     "@types/inquirer": "9.0.9",
     "@types/jest": "29.5.14",
     "@types/node": "24.10.1",
     "@types/node-emoji": "1.8.2",
     "@types/webpack-node-externals": "3.0.4",
-    "@typescript-eslint/eslint-plugin": "8.47.0",
-    "@typescript-eslint/parser": "8.47.0",
+    "@typescript-eslint/eslint-plugin": "8.48.0",
+    "@typescript-eslint/parser": "8.48.0",
     "delete-empty": "3.0.0",
     "eslint": "9.39.1",
     "eslint-config-prettier": "10.1.8",
@@ -76,8 +76,8 @@
     "gulp-clean": "0.4.0",
     "husky": "9.1.7",
     "jest": "29.7.0",
-    "lint-staged": "16.2.6",
-    "prettier": "3.6.2",
+    "lint-staged": "16.2.7",
+    "prettier": "3.7.1",
     "release-it": "19.0.6",
     "ts-jest": "29.4.5",
     "ts-loader": "9.5.4",

package/.circleci/config.yml

@@ -1,61 +0,0 @@
-version: 2
-
-aliases:
-  - &restore-cache
-    restore_cache:
-      key: dependency-cache-{{ checksum "package.json" }}
-  - &install-deps
-    run:
-      name: Install dependencies
-      command: npm install --ignore-scripts --legacy-peer-deps
-  - &build-packages
-    run:
-      name: Build
-      command: npm run build
-  - &run-unit-tests
-    run:
-      name: Test
-      command: npm run test -- --runInBand --no-cache
-
-jobs:
-  build:
-    working_directory: ~/nest
-    docker:
-      - image: cimg/node:24.11.1
-    steps:
-      - checkout
-      - restore_cache:
-          key: dependency-cache-{{ checksum "package.json" }}
-      - run:
-          name: Install dependencies
-          command: npm install --ignore-scripts --legacy-peer-deps
-      - save_cache:
-          key: dependency-cache-{{ checksum "package.json" }}
-          paths:
-            - ./node_modules
-      - run:
-          name: Build
-          command: npm run build
-
-  unit_tests:
-    working_directory: ~/nest
-    docker:
-      - image: cimg/node:24.11.1
-    steps:
-      - checkout
-      - *restore-cache
-      - *install-deps
-      - *build-packages
-      - run:
-          name: Clean build artifacts
-          command: npm run clean
-      - *run-unit-tests
-
-workflows:
-  version: 2
-  build-and-test:
-    jobs:
-      - build
-      - unit_tests:
-          requires:
-            - build

package/.github/ISSUE_TEMPLATE/Bug_report.yml

@@ -1,106 +0,0 @@
-name: "\U0001F41B Bug Report"
-description: "If something isn't working as expected \U0001F914"
-labels: ["needs triage", "bug"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## :warning: We use GitHub Issues to track bug reports, feature requests and regressions
- 
-        If you are not sure that your issue is a bug, you could:
-
-        - use our [Discord community](https://discord.gg/NestJS)
-        - use [StackOverflow using the tag `nestjs`](https://stackoverflow.com/questions/tagged/nestjs)
-        - If it's just a quick question you can ping [our Twitter](https://twitter.com/nestframework)
-
-        **NOTE:** You don't need to answer questions that you know that aren't relevant.
-
-        ---
-
-  - type: checkboxes
-    attributes:
-      label: "Is there an existing issue for this?"
-      description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the bug you encountered"
-      options:
-      - label: "I have searched the existing issues"
-        required: true
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "Current behavior"
-      description: "How the issue manifests?"
-
-  - type: input
-    validations:
-      required: true
-    attributes:
-      label: "Minimum reproduction code"
-      description: "An URL to some git repository or gist that reproduces this issue. [Wtf is a minimum reproduction?](https://jmcdo29.github.io/wtf-is-a-minimum-reproduction)"
-      placeholder: "https://github.com/..."
-
-  - type: textarea
-    attributes:
-      label: "Steps to reproduce"
-      description: |
-        How the issue manifests?
-        You could leave this blank if you alread write this in your reproduction code/repo
-      placeholder: |
-        1. `npm i`
-        2. `npm start:dev`
-        3. See error...
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "Expected behavior"
-      description: "A clear and concise description of what you expected to happend (or code)"
-
-  - type: markdown
-    attributes:
-      value: |
-        ---
-
-  - type: input
-    validations:
-      required: true
-    attributes:
-      label: "Package version"
-      description: |
-        Which version of `@nestjs/cli` are you using?
-        **Tip**: Make sure that all of yours `@nestjs/*` dependencies are in sync!
-      placeholder: "8.1.3"
-
-  - type: input
-    attributes:
-      label: "NestJS version"
-      description: "Which version of `@nestjs/core` are you using?"
-      placeholder: "8.1.3"
-
-  - type: input
-    attributes:
-      label: "Node.js version"
-      description: "Which version of Node.js are you using?"
-      placeholder: "14.17.6"
-
-  - type: checkboxes
-    attributes:
-      label: "In which operating systems have you tested?"
-      options:
-        - label: macOS
-        - label: Windows
-        - label: Linux
-
-  - type: markdown
-    attributes:
-      value: |
-        ---
-
-  - type: textarea
-    attributes:
-      label: "Other"
-      description: |
-        Anything else relevant? eg: Logs, OS version, IDE, package manager, etc.
-        **Tip:** You can attach images, recordings or log files by clicking this area to highlight it and then dragging files in

package/.github/ISSUE_TEMPLATE/Feature_request.yml

@@ -1,52 +0,0 @@
-name: "\U0001F680 Feature Request"
-description: "I have a suggestion \U0001F63B!"
-labels: ["feature"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## :warning: We use GitHub Issues to track bug reports, feature requests and regressions
- 
-        If you are not sure that your issue is a bug, you could:
-
-        - use our [Discord community](https://discord.gg/NestJS)
-        - use [StackOverflow using the tag `nestjs`](https://stackoverflow.com/questions/tagged/nestjs)
-        - If it's just a quick question you can ping [our Twitter](https://twitter.com/nestframework)
-
-        ---
-
-  - type: checkboxes
-    attributes:
-      label: "Is there an existing issue that is already proposing this?"
-      description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the feature you are requesting"
-      options:
-      - label: "I have searched the existing issues"
-        required: true
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "Is your feature request related to a problem? Please describe it"
-      description: "A clear and concise description of what the problem is"
-      placeholder: |
-        I have an issue when ...
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "Describe the solution you'd like"
-      description: "A clear and concise description of what you want to happen. Add any considered drawbacks"
-
-  - type: textarea
-    attributes:
-      label: "Teachability, documentation, adoption, migration strategy"
-      description: "If you can, explain how users will be able to use this and possibly write out a version the docs. Maybe a screenshot or design?"
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "What is the motivation / use case for changing the behavior?"
-      description: "Describe the motivation or the concrete use case"

package/.github/ISSUE_TEMPLATE/Regression.yml

@@ -1,78 +0,0 @@
-name: "\U0001F4A5 Regression"
-description: "Report an unexpected behavior while upgrading your Nest application!"
-labels: ["needs triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## :warning: We use GitHub Issues to track bug reports, feature requests and regressions
- 
-        If you are not sure that your issue is a bug, you could:
-
-        - use our [Discord community](https://discord.gg/NestJS)
-        - use [StackOverflow using the tag `nestjs`](https://stackoverflow.com/questions/tagged/nestjs)
-        - If it's just a quick question you can ping [our Twitter](https://twitter.com/nestframework)
-
-        **NOTE:** You don't need to answer questions that you know that aren't relevant.
-
-        ---
-
-  - type: checkboxes
-    attributes:
-      label: "Did you read the migration guide?"
-      description: "Check out the [migration guide here](https://docs.nestjs.com/migration-guide)!"
-      options:
-      - label: "I have read the whole migration guide"
-        required: false
-
-  - type: checkboxes
-    attributes:
-      label: "Is there an existing issue that is already proposing this?"
-      description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the feature you are requesting"
-      options:
-      - label: "I have searched the existing issues"
-        required: true
-
-  - type: input
-    attributes:
-      label: "Potential Commit/PR that introduced the regression"
-      description: "If you have time to investigate, what PR/date/version introduced this issue"
-      placeholder: "PR #123 or commit 5b3c4a4"
-
-  - type: input
-    attributes:
-      label: "Versions"
-      description: "From which version of `@nestjs/cli` to which version you are upgrading"
-      placeholder: "8.1.0 -> 8.1.3"
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "Describe the regression"
-      description: "A clear and concise description of what the regression is"
-
-  - type: textarea
-    attributes:
-      label: "Minimum reproduction code"
-      description: |
-        Please share a git repo, a gist, or step-by-step instructions. [Wtf is a minimum reproduction?](https://jmcdo29.github.io/wtf-is-a-minimum-reproduction)
-        **Tip:** If you leave a minimum repository, we will understand your issue faster!
-      value: |
-        ```ts
-
-        ```
-
-  - type: textarea
-    validations:
-      required: true
-    attributes:
-      label: "Expected behavior"
-      description: "A clear and concise description of what you expected to happend (or code)"
-
-  - type: textarea
-    attributes:
-      label: "Other"
-      description: |
-        Anything else relevant? eg: Logs, OS version, IDE, package manager, etc.
-        **Tip:** You can attach images, recordings or log files by clicking this area to highlight it and then dragging files in

package/.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +0,0 @@
-## To encourage contributors to use issue templates, we don't allow blank issues
-blank_issues_enabled: false
-
-contact_links:
-  - name: "\u2753 Discord Community of NestJS"
-    url: "https://discord.gg/NestJS"
-    about: "Please ask support questions or discuss suggestions/enhancements here."

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,41 +0,0 @@
-## PR Checklist
-Please check if your PR fulfills the following requirements:
-
-- [ ] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
-- [ ] Tests for the changes have been added (for bug fixes / features)
-- [ ] Docs have been added / updated (for bug fixes / features)
-
-
-## PR Type
-What kind of change does this PR introduce?
-
-<!-- Please check the one that applies to this PR using "x". -->
-```
-[ ] Bugfix
-[ ] Feature
-[ ] Code style update (formatting, local variables)
-[ ] Refactoring (no functional changes, no api changes)
-[ ] Build related changes
-[ ] CI related changes
-[ ] Other... Please describe:
-```
-
-## What is the current behavior?
-<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
-
-Issue Number: N/A
-
-
-## What is the new behavior?
-
-
-## Does this PR introduce a breaking change?
-```
-[ ] Yes
-[ ] No
-```
-
-<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
-
-
-## Other information

package/.husky/commit-msg

@@ -1 +0,0 @@
-npx --no-install commitlint --edit $1

package/.husky/pre-commit

@@ -1 +0,0 @@
-npx --no-install lint-staged

package/CONTRIBUTING.md

@@ -1,226 +0,0 @@
-# Contributing to Nest CLI
-
-We would love for you to contribute to Nest and help make it even better than it is today! As a contributor, here are the guidelines we would like you to follow :
-
-- [Question or Problem?](#question)
-- [Issues and Bugs](#issue)
-- [Feature Requests](#feature)
-- [Submission Guidelines](#submit)
-
-## <a name="question"></a> Got a Question or Problem ?
-
-**Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests.** You've got much better chances of getting your question answered on Stack Overflow where the questions should be tagged with tag nestjs.
-
-[Stack Overflow](https://stackoverflow.com/questions/tagged/nestjs) is a much better place to ask questions since:
-
-- questions and answers stay available for public viewing so your question / answer might help someone else
-- Stack Overflow's voting system assures that the best answers are prominently visible.
-
-To save your and our time, we will systematically close all issues that are requests for general support and redirect people to Stack Overflow.
-
-If you would like to chat about the question in real-time, you can reach out via [our discord channel][discord].
-
-## <a name="issue"></a> Found a Bug?
-
-If you find a bug in the source code, you can help us by
-[submitting an issue](#submit-issue). Even better, you can [submit a Pull Request](#submit-pr) with a fix.
-
-## <a name="feature"></a> Missing a Feature?
-
-You can _request_ a new feature by [submitting an issue](#submit-issue) to our GitHub
-Repository. If you would like to _implement_ a new feature, please submit an issue with
-a proposal for your work first, to be sure that we can use it.
-Please consider what kind of change it is:
-
-- For a **Major Feature**, first open an issue and outline your proposal so that it can be
-  discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
-  and help you to craft the change so that it is successfully accepted into the project. For your issue name, please prefix your proposal with `[discussion]`, for example "[discussion]: your feature idea".
-- **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
-
-## <a name="submit"></a> Submission Guidelines
-
-### <a name="submit-issue"></a> Submitting an Issue
-
-Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
-
-We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will systematically ask you to provide a minimal reproduction scenario using a repository or [Gist](https://gist.github.com/). Having a live, reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like:
-
-- version of NestJS-CLI used (`nest info`)
-- and most importantly - a use-case that fails
-
-Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that doesn't have enough info to be reproduced.
-
-You can file new issues by filling out our [new issue form](https://github.com/nestjs/nest/issues/new).
-
-### <a name="submit-pr"></a> Submitting a Pull Request (PR)
-
-Before you submit your Pull Request (PR) consider the following guidelines:
-
-1. Search [GitHub](https://github.com/nestjs/nest/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort.
-1. Fork the nestjs/nest-cli repo.
-1. Get a gpg key to sign your commits, see [help](https://help.github.com/articles/about-gpg/).
-1. Create your patch, **including appropriate test cases**.
-1. Commit your changes using a descriptive commit message
-
-   ```shell
-   git commit -am "<message>"
-   ```
-
-   Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
-
-1. Push your branch to GitHub:
-
-   ```shell
-   git push origin my-fix-branch
-   ```
-
-   Note: you can use -u to set your branch in upstream and just push for the next times.
-
-1. In GitHub, send a pull request to `nestjs/nest-cli:master`.
-
-- If we suggest changes then:
-
-  - Make the required updates.
-  - Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
-
-    ```shell
-    git rebase master -i
-    git push -f
-    ```
-
-That's it! Thank you for your contribution!
-
-#### After your pull request is merged
-
-After your pull request is merged, you can safely delete your branch and pull the changes
-from the main (upstream) repository:
-
-- Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
-
-  ```shell
-  git push origin --delete my-fix-branch
-  ```
-
-- Check out the master branch:
-
-  ```shell
-  git checkout master -f
-  ```
-
-- Delete the local branch:
-
-  ```shell
-  git branch -D my-fix-branch
-  ```
-
-- Update your master with the latest upstream version:
-
-  ```shell
-  git pull --ff upstream master
-  ```
-
-  ## <a name="rules"></a> Coding Rules
-To ensure consistency throughout the source code, keep these rules in mind as you are working:
-
-* All features or bug fixes **must be tested** by one or more specs (unit-tests).
-<!--
-// We're working on auto-documentation.
-* All public API methods **must be documented**. (Details TBC). -->
-* We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at
-  **100 characters**. An automated formatter is available ( `npm run format` ).
-
-## <a name="commit"></a> Commit Message Guidelines
-
-We have very precise rules over how our git commit messages can be formatted.  This leads to **more
-readable messages** that are easy to follow when looking through the **project history**.  But also,
-we use the git commit messages to **generate the Nest change log**.
-
-### Commit Message Format
-Each commit message consists of a **header**, a **body** and a **footer**.  The header has a special
-format that includes a **type**, a **scope** and a **subject**:
-
-```
-<type>(<scope>): <subject>
-<BLANK LINE>
-<body>
-<BLANK LINE>
-<footer>
-```
-
-The **header** is mandatory and the **scope** of the header is optional.
-
-Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier
-to read on GitHub as well as in various git tools.
-
-Footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
-
-Samples: (even more [samples](https://github.com/nestjs/nest/commits/master))
-
-```
-docs(changelog) update change log to beta.5
-```
-```
-fix(@nestjs/core) need to depend on latest rxjs and zone.js
-
-The version in our package.json gets copied to the one we publish, and users need the latest of these.
-```
-
-### Revert
-If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
-
-### Type
-Must be one of the following:
-
-* **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
-* **chore**: Updating tasks etc; no production code change
-* **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
-* **docs**: Documentation only changes
-* **feat**: A new feature
-* **fix**: A bug fix
-* **perf**: A code change that improves performance
-* **refactor**: A code change that neither fixes a bug nor adds a feature
-* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
-* **test**: Adding missing tests or correcting existing tests
-
-
-### Subject
-The subject contains succinct description of the change:
-
-* use the imperative, present tense: "change" not "changed" nor "changes"
-* don't capitalize first letter
-* no dot (.) at the end
-
-### Body
-Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
-The body should include the motivation for the change and contrast this with previous behavior.
-
-### Footer
-The footer should contain any information about **Breaking Changes** and is also the place to
-reference GitHub issues that this commit **Closes**.
-
-**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
-
-A detailed explanation can be found in this [document][commit-message-format].
-
-<!-- ## <a name="cla"></a> Signing the CLA
-
-Please sign our Contributor License Agreement (CLA) before sending pull requests. For any code
-changes to be accepted, the CLA must be signed. It's a quick process, we promise!
-
-* For individuals we have a [simple click-through form][individual-cla].
-* For corporations we'll need you to
-  [print, sign and one of scan+email, fax or mail the form][corporate-cla]. -->
-
-
-<!-- [angular-group]: https://groups.google.com/forum/#!forum/angular -->
-<!-- [coc]: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md -->
-[commit-message-format]: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#
-[corporate-cla]: http://code.google.com/legal/corporate-cla-v1.0.html
-[github]: https://github.com/nestjs/nest
-[discord]: https://discord.gg/nestjs
-[individual-cla]: http://code.google.com/legal/individual-cla-v1.0.html
-[js-style-guide]: https://google.github.io/styleguide/jsguide.html
-[jsfiddle]: http://jsfiddle.net
-[plunker]: http://plnkr.co/edit
-[runnable]: http://runnable.com
-<!-- [stackoverflow]: http://stackoverflow.com/questions/tagged/angular -->

package/test/lib/compiler/hooks/__snapshots__/tsconfig-paths.hook.spec.ts.snap

@@ -1,68 +0,0 @@
-// Jest Snapshot v1, https://goo.gl/fbAQLP
-
-exports[`tsconfig paths hooks should remove unused imports 1`] = `
-Map {
-  "dist/foo.js" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Foo = void 0;
-class Foo {
-}
-exports.Foo = Foo;
-",
-  "dist/bar.js" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Bar = void 0;
-class Bar {
-}
-exports.Bar = Bar;
-",
-  "dist/main.js" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-",
-}
-`;
-
-exports[`tsconfig paths hooks should replace path of every import using a path alias by its relative path 1`] = `
-Map {
-  "dist/foo.js" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Foo = void 0;
-class Foo {
-}
-exports.Foo = Foo;
-",
-  "dist/bar.jsx" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Bar = void 0;
-class Bar {
-}
-exports.Bar = Bar;
-",
-  "dist/baz.js" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Baz = void 0;
-class Baz {
-}
-exports.Baz = Baz;
-",
-  "dist/qux.jsx" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Qux = void 0;
-class Qux {
-}
-exports.Qux = Qux;
-",
-  "dist/main.js" => ""use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-const foo_1 = require("./foo");
-const bar_1 = require("./bar");
-const baz_1 = require("./baz");
-const qux_1 = require("./qux");
-// use the imports so they do not get eliminated
-console.log(foo_1.Foo);
-console.log(bar_1.Bar);
-console.log(baz_1.Baz);
-console.log(qux_1.Qux);
-",
-}
-`;

package/test/lib/compiler/hooks/fixtures/aliased-imports/src/bar.tsx

@@ -1 +0,0 @@
-export class Bar {}

package/test/lib/compiler/hooks/fixtures/aliased-imports/src/baz.js

@@ -1 +0,0 @@
-export class Baz {}

package/test/lib/compiler/hooks/fixtures/aliased-imports/src/qux.jsx

@@ -1 +0,0 @@
-export class Qux {}

package/test/lib/schematics/fixtures/extended/collection.json

@@ -1,26 +0,0 @@
-{
-  "$schema": "../../../../../node_modules/@angular-devkit/schematics/collection-schema.json",
-  "extends": ["../simple/collection.json"],
-  "schematics": {
-    "simple1": {
-      "factory": "factory",
-      "description": "Override schematic 1",
-      "aliases": ["s1", "simp1"]
-    },
-    "simple2": {
-      "factory": "factory",
-      "description": "Override schematic 2",
-      "aliases": ["os2", "s2", "simp2"]
-    },
-    "extend1": {
-      "factory": "factory",
-      "description": "Extended schematic 1",
-      "aliases": ["x1", "ext1"]
-    },
-    "extend2": {
-      "factory": "factory",
-      "description": "Extended schematic 2",
-      "aliases": ["x2", "ext2", "s3", "simp3"]
-    }
-  }
-}

package/test/lib/schematics/fixtures/package/a/b/c/collection.json

@@ -1,10 +0,0 @@
-{
-  "$schema": "../../../../../../../../node_modules/@angular-devkit/schematics/collection-schema.json",
-  "schematics": {
-    "package1": {
-      "factory": "factory",
-      "description": "Package schematic 1",
-      "aliases": ["pkg1"]
-    }
-  }
-}

package/test/lib/schematics/fixtures/package/package.json

@@ -1,5 +0,0 @@
-{
-  "name": "package",
-  "version": "0.0.0",
-  "schematics": "./a/b/c/collection.json"
-}

package/test/lib/schematics/fixtures/simple/collection.json

@@ -1,20 +0,0 @@
-{
-  "$schema": "../../../../../node_modules/@angular-devkit/schematics/collection-schema.json",
-  "schematics": {
-    "simple1": {
-      "factory": "factory",
-      "description": "Simple schematic 1",
-      "aliases": ["s1", "simp1"]
-    },
-    "simple2": {
-      "factory": "factory",
-      "description": "Simple schematic 2",
-      "aliases": ["s2", "simp2"]
-    },
-    "simple3": {
-      "factory": "factory",
-      "description": "Simple schematic 3",
-      "aliases": ["s3", "simp3"]
-    }
-  }
-}