mirror of https://github.com/angular/angular-cli.git synced 2025-05-16 18:43:42 +08:00

History

Paul Gschwendtner 9dd3f0344f

Further clean-up rules_nodejs npm workspace and remove yarn.lock (#29779 )

* build: disconnect `@npm` workspace from main project

This will speed up significantly as we don't need to fetch all
dependencies again just for the `@npm` repository that is at this point
only leveraged by the `ng_package` rule for some of its dependencies.

This commit allows us to drop the `yarn.lock` and Aspect lock files, and
allows us to independently migrate `ng_package` to `rules_js`.

It also allows us to drop the `_rjs` TS interop layer in follow-up commits.

* build: drop `_rjs` suffix from `ts_project` targets

We don't need the `ts_project` interop in principle
at this point. We only have one remaining instance left for the SSR
`ng_package` integration. This commit cleans up all usages.

* build: remove yarn

* build: avoid duplicated dependencies at top-level

`rules_js` seems to be sensitive if there are similar versions of the same
package installed, but with differently matched peer dependencies. This
is fine because we can (and should long-term) move those dependencies to
their package-local `package.json` files. This commit unblocks the
migration and highlights how we can move deps to the individual packages
in the future.

* build: update checkout github action

This will allow us to use pnpm.

* build: update node to avoid strict-engines error caused by `npm`

Avoids:

```
Lockfile is up to date, resolution step is skipped
ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)

Your Node version is incompatible with "npm@11.2.0".

Expected version: ^20.17.0 || >=22.9.0
Got: v20.11.1
```

Note that we won't update the WORKSPACE test version as that would mean
we need to update the Node engines for shipped packages; and we can't do
this right now without introducing a breaking change.

* build: fix missing dependency for spec bundling

The beasties JS sources weren't available for bundling in the
`bazel-bin`, and this surfaced in RBE. This commit fixes this.

2025-03-11 10:05:52 +01:00

pwa

fix(@schematics/angular): add additional checks for application builder usage

2025-02-24 18:34:09 -05:00

BUILD.bazel

Further clean-up rules_nodejs npm workspace and remove yarn.lock (#29779 )

2025-03-11 10:05:52 +01:00

collection.json

fix(@angular/pwa): additional public schematic definition

2019-11-26 13:06:06 -08:00

package.json

build: migrate @angular/pwa tests to rules_js

2025-01-21 09:25:54 +01:00

README.md

refactor(@angular/cli): update aio links -> adev links

2024-06-06 11:12:06 +02:00

README.md

`@angular/pwa`

This is a schematic for adding Progressive Web App support to an Angular project. Run the schematic with the Angular CLI:

ng add @angular/pwa --project <project-name>

Executing the command mentioned above will perform the following actions:

Adds @angular/service-worker as a dependency to your project.
Enables service worker builds in the Angular CLI.
Imports and registers the service worker in the application module.
Updates the index.html file:
- Includes a link to add the manifest.webmanifest file.
- Adds a meta tag for theme-color.
Installs icon files to support the installed Progressive Web App (PWA).
Creates the service worker configuration file called ngsw-config.json, specifying caching behaviors and other settings.

See Getting started with service workers for more information.