ngworker / ngworker

Monorepo for the @ngworker NPM organization. Packages for Angular applications and testing.

@ngworker/* monorepo

Monorepo for the ngworker NPM organization. Packages for Angular applications.

Packages

Packages in this monorepo.

Package	Description
Spectacular (@ngworker/spectacular)	Spectacular Angular integration testing. Test harnesses for Angular applications and libraries.

Sponsors

Wallaby 🦘

The maintainers of ngworker use Wallaby.js for inline test feeedback sponsored by Wallaby. Get your free OSS license at the Wallaby website.

Contributors to this repository are welcome to use the Wallaby.js OSS License to get test results immediately as you type, and see the results in your editor right next to your code.

Nrwl 🌊

Nrwl sponsors computation hours saved for ngworker through Nx Cloud ☁. Apply for a free license for your OSS project at [email protected] or watch ngworker's Nx Cloud runs and cache stats on nx.app.

Computation Memoization in the Cloud

Nx Cloud pairs with Nx in order to enable you to build and test code more rapidly, by up to 10 times. Even teams that are new to Nx can connect to Nx Cloud and start saving time instantly.

Teams using Nx gain the advantage of building full-stack applications with their preferred framework alongside Nx’s advanced code generation and project dependency graph, plus a unified experience for both frontend and backend developers.

Visit Nx Cloud to learn more.

Contributors

Thanks goes to these wonderful people:

Lars Gyrup Brink Nielsen 💬 🐛 💻 📖 💡 🤔 🚇 🚧 🧑‍🏫 📦 🔌 📆 👀 ⚠️

Santosh Yadav 💬 💻 📖 🤔 👀 ⚠️

Bitcollage 💬 🐛 💻 💡 🤔 🚇 🚧 📦 👀 ⚠️

Nacho Vazquez 💬 🐛 💻 📖 💡 🤔 🚇 📦 👀 ⚠️

Tim Deschryver 📖

(emoji key)

This project follows the all-contributors specification. Contributions of any kind welcome!

ngworker's Issues

spectacular: the application harness fails when using asynchronous application initializers

Describe the bug

The application test harness fails when testing asynchronous application initializers.

To Reproduce

1. Register an asynchronous application initializer through createApplicationHarness.
2. An error is thrown or the application hooks are not run.

Expected behavior

No errors are thrown and the application hooks are run.

Screenshots

Environment

  Node : 12.20.1
  OS   : win32 x64
  pnpm : 5.15.1
  
  nx : Not Found
  @nrwl/angular : 11.2.10
  @nrwl/cli : 11.2.10
  @nrwl/cypress : 11.2.10
  @nrwl/devkit : 11.2.10
  @nrwl/eslint-plugin-nx : 11.2.10
  @nrwl/express : Not Found
  @nrwl/jest : 11.2.10
  @nrwl/linter : 11.2.10
  @nrwl/nest : Not Found
  @nrwl/next : Not Found
  @nrwl/node : 11.2.10
  @nrwl/react : Not Found
  @nrwl/schematics : Not Found
  @nrwl/tao : 11.2.10
  @nrwl/web : Not Found
  @nrwl/workspace : 11.2.10
  typescript : 4.0.5

Additional context

spectacular: support standalone pipe testing

Describe the bug

Support standalone pipe testing.

To Reproduce

1. Pass a standalone pipe to the pipe option of createPipeHarness
2. Run the test
3. Check the test runner's output
4. See error

Unexpected "StandalonePipe" found in the "declarations" array of the "DynamicTestModule" NgModule, "StandalonePipe" is marked as standalone and can't be declared in any NgModule - did you intend to import it instead (by adding it to the "imports" array)?

Expected behavior

No errors when passing a standalone pipe to the pipe option of createPipeHarness

Environment

Spectacular version: 0.5.0

Nx report

   Node : 18.15.0
   OS   : win32 x64
   yarn : 3.3.1
   
   nx : 15.5.3
   @nrwl/angular : 15.5.3
   @nrwl/cypress : 15.5.3
   @nrwl/detox : Not Found
   @nrwl/devkit : 15.5.3
   @nrwl/esbuild : Not Found
   @nrwl/eslint-plugin-nx : 15.5.3
   @nrwl/expo : Not Found
   @nrwl/express : Not Found
   @nrwl/jest : 15.5.3
   @nrwl/js : 15.5.3
   @nrwl/linter : 15.5.3
   @nrwl/nest : Not Found
   @nrwl/next : Not Found
   @nrwl/node : Not Found
   @nrwl/nx-cloud : Not Found
   @nrwl/nx-plugin : Not Found
   @nrwl/react : Not Found
   @nrwl/react-native : Not Found
   @nrwl/rollup : Not Found
   @nrwl/schematics : Not Found
   @nrwl/storybook : 15.5.3
   @nrwl/web : Not Found
   @nrwl/webpack : 15.5.3
   @nrwl/workspace : 15.5.3
   @nrwl/vite : Not Found
   typescript : 4.9.4

Additional context

Standalone pipes were introduced in Angular 14.0.

isStandalone was introduced in Angular 15.1. We can use isStandalone to detect whether a pipe is a standalone pipe or a classic pipe.

Funding

• You can sponsor this specific effort via a Polar.sh pledge below
• We receive 90% of the pledge once the issue is completed & verified
• Polar receives 10% of the pledge as a fee

spectacular: The pipe testing harness doesn't work with Angular >=13.1

Describe the bug

PipeResolver is used internally by Spectacular 0.3.0 but is removed in Angular 13.1.

To Reproduce

1. Install Angular 13.1.0.
2. Install Spectacular.
3. Create pipe harness.
4. Test fails due to compilation error.

Expected behavior

1. Install Angular 13.1.0.
2. Install Spectacular.
3. Create pipe harness.
4. Test passes.

Screenshots

Environment

Additional context

Reported by @dzhavat.

docs: replace `set-output` GitHub Actions command

What is the motivation/use case for changing the behavior?

The docs job outputs the following error

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Describe the solution you'd like

Describe alternatives you've considered

Additional context

spectacular: is it possible to see if an Injector has been called?

Describe the solution you'd like

Spectator has a possibility to do something like this:
expect(spectator.inject(ApplicationAPIService).getAttachments).toHaveBeenCalled()

I'm not familiarwith the @testing-library yet, so I hope there's a way to fulfill this one.
Thanks in advance!

docs: replace `JamesIves/github-pages-deploy-action` with `actions/deploy-pages`

What is the motivation/use case for changing the behavior?

The docs job outputs the following error

The following actions uses node12 which is deprecated and will be forced to run on node16: JamesIves/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Describe the solution you'd like

Describe alternatives you've considered

Additional context

spectacular: Support for Angular 13

What is the motivation/use case for changing the behavior?

No change to behavior

Describe the solution you'd like

npm install --save-dev @ngworker/spectacular - installs as dev dependency

Describe alternatives you've considered

Haven't considered any alternatives at the moment

Additional context

npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^13.1.3" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^11.0.9" from @ngworker/[email protected]
npm ERR! node_modules/@ngworker/spectacular
npm ERR! dev @ngworker/spectacular@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.