mirror of https://github.com/flutter/samples.git synced 2026-06-12 17:28:52 +00:00

Files

dependabot[bot] 80069cd272 Bump @angular-devkit/build-angular from 21.2.14 to 22.0.1 in /web_embedding/ng-flutter (#2853 )

⚠️  **Dependabot is rebasing this PR** ⚠️ 

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps [@angular-devkit/build-angular](https://github.com/angular/angular-cli) from 21.2.14 to 22.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/angular/angular-cli/releases">@angular-devkit/build-angular's releases</a>.</em></p>
<blockquote>
<h2>22.0.1</h2>
<h3><code>@schematics/angular</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="c800122945"><img src="https://img.shields.io/badge/c80012294-fix-green" alt="fix - c80012294" /></a></td>
<td>fix browserMode option mapping in refactor-jasmine-vitest</td>
</tr>
<tr>
<td><a href="a9b6bd9042"><img src="https://img.shields.io/badge/a9b6bd904-fix-green" alt="fix - a9b6bd904" /></a></td>
<td>safely comment out multiline statements in refactor-jasmine-vitest</td>
</tr>
<tr>
<td><a href="12199df00f"><img src="https://img.shields.io/badge/12199df00-fix-green" alt="fix - 12199df00" /></a></td>
<td>use null objects and callbacks in karma-to-vitest migration</td>
</tr>
</tbody>
</table>
<h3><code>@angular/cli</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="b54e9a549d"><img src="https://img.shields.io/badge/b54e9a549-fix-green" alt="fix - b54e9a549" /></a></td>
<td>do not sort migrations of the same version alphabetically</td>
</tr>
<tr>
<td><a href="d333116123"><img src="https://img.shields.io/badge/d33311612-fix-green" alt="fix - d33311612" /></a></td>
<td>fallback to local package.json for schematic detection on first run</td>
</tr>
<tr>
<td><a href="918102a937"><img src="https://img.shields.io/badge/918102a93-fix-green" alt="fix - 918102a93" /></a></td>
<td>isolate temporary package installation from parent pnpm workspace</td>
</tr>
<tr>
<td><a href="b048b5f4a8"><img src="https://img.shields.io/badge/b048b5f4a-fix-green" alt="fix - b048b5f4a" /></a></td>
<td>remove forceAuth and unscoped credential parsing</td>
</tr>
<tr>
<td><a href="2779340351"><img src="https://img.shields.io/badge/277934035-fix-green" alt="fix - 277934035" /></a></td>
<td>validate registry option is a valid URL in ng add</td>
</tr>
<tr>
<td><a href="4510dae021"><img src="https://img.shields.io/badge/4510dae02-perf-orange" alt="perf - 4510dae02" /></a></td>
<td>optimize update schematic registry query counts by fetching package metadata lazily</td>
</tr>
</tbody>
</table>
<h3><code>@angular/build</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="89d1be979f"><img src="https://img.shields.io/badge/89d1be979-fix-green" alt="fix - 89d1be979" /></a></td>
<td>allow disabling Vitest isolation from builder</td>
</tr>
<tr>
<td><a href="d45b84be9a"><img src="https://img.shields.io/badge/d45b84be9-fix-green" alt="fix - d45b84be9" /></a></td>
<td>exclude JSON imports from Vite dependency optimization</td>
</tr>
<tr>
<td><a href="e3cab4ddda"><img src="https://img.shields.io/badge/e3cab4ddd-fix-green" alt="fix - e3cab4ddd" /></a></td>
<td>prevent concurrent stylesheet bundling esbuild context leaks</td>
</tr>
<tr>
<td><a href="bd413b0eb1"><img src="https://img.shields.io/badge/bd413b0eb-fix-green" alt="fix - bd413b0eb" /></a></td>
<td>restrict application builder output paths to output directory</td>
</tr>
</tbody>
</table>
<h2>22.0.0</h2>
<h3><code>@schematics/angular</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="be60a63b7b"><img src="https://img.shields.io/badge/be60a63b7-feat-blue" alt="feat - be60a63b7" /></a></td>
<td>add migrate-karma-to-vitest update migration</td>
</tr>
<tr>
<td><a href="43505066e2"><img src="https://img.shields.io/badge/43505066e-feat-blue" alt="feat - 43505066e" /></a></td>
<td>add migration to add istanbul-lib-instrument</td>
</tr>
<tr>
<td><a href="b2f7a038b4"><img src="https://img.shields.io/badge/b2f7a038b-feat-blue" alt="feat - b2f7a038b" /></a></td>
<td>conditionally install istanbul coverage provider for Vitest migration</td>
</tr>
<tr>
<td><a href="d227e6985e"><img src="https://img.shields.io/badge/d227e6985-feat-blue" alt="feat - d227e6985" /></a></td>
<td>migrate fake async to Vitest fake timers</td>
</tr>
<tr>
<td><a href="d2aa9ede55"><img src="https://img.shields.io/badge/d2aa9ede5-feat-blue" alt="feat - d2aa9ede5" /></a></td>
<td>migrate fakeAsync's flush behavior when used in beforeEach</td>
</tr>
<tr>
<td><a href="f98cc82eb0"><img src="https://img.shields.io/badge/f98cc82eb-feat-blue" alt="feat - f98cc82eb" /></a></td>
<td>rely on strict template default in generated workspaces</td>
</tr>
<tr>
<td><a href="c9f4081533"><img src="https://img.shields.io/badge/c9f408153-feat-blue" alt="feat - c9f408153" /></a></td>
<td>set up fake timers in beforeEach instead of beforeAll</td>
</tr>
<tr>
<td><a href="de630c2fce"><img src="https://img.shields.io/badge/de630c2fc-feat-blue" alt="feat - de630c2fc" /></a></td>
<td>stabilize refactor-jasmine-vitest schematic</td>
</tr>
<tr>
<td><a href="8d0805dd17"><img src="https://img.shields.io/badge/8d0805dd1-feat-blue" alt="feat - 8d0805dd1" /></a></td>
<td>update TSConfig globals during karma to vitest migration</td>
</tr>
<tr>
<td><a href="470e1f9374"><img src="https://img.shields.io/badge/470e1f937-fix-green" alt="fix - 470e1f937" /></a></td>
<td>add istanbul-lib-instrument to application/library generator dependencies</td>
</tr>
<tr>
<td><a href="dc1238e5a4"><img src="https://img.shields.io/badge/dc1238e5a-fix-green" alt="fix - dc1238e5a" /></a></td>
<td>add trusted-proxy-headers migration</td>
</tr>
<tr>
<td><a href="6572a69443"><img src="https://img.shields.io/badge/6572a6944-fix-green" alt="fix - 6572a6944" /></a></td>
<td>default components to OnPush change detection</td>
</tr>
<tr>
<td><a href="aed407db8b"><img src="https://img.shields.io/badge/aed407db8-fix-green" alt="fix - aed407db8" /></a></td>
<td>defer karma config deletion in Karma to Vitest migration</td>
</tr>
<tr>
<td><a href="4fbc608917"><img src="https://img.shields.io/badge/4fbc60891-fix-green" alt="fix - 4fbc60891" /></a></td>
<td>preserve Jasmine stub-by-default semantics for bare spies</td>
</tr>
<tr>
<td><a href="b3d838dfdb"><img src="https://img.shields.io/badge/b3d838dfd-fix-green" alt="fix - b3d838dfd" /></a></td>
<td>replace deprecated <code>ChangeDetectionStrategy.Default</code> with <code>Eager</code></td>
</tr>
<tr>
<td><a href="a7ac8e5f0a"><img src="https://img.shields.io/badge/a7ac8e5f0-fix-green" alt="fix - a7ac8e5f0" /></a></td>
<td>support spy call arguments migration in refactor-jasmine-vitest</td>
</tr>
<tr>
<td><a href="7fb59eaa65"><img src="https://img.shields.io/badge/7fb59eaa6-fix-green" alt="fix - 7fb59eaa6" /></a></td>
<td>use service decorator in ng generate</td>
</tr>
</tbody>
</table>
<h3><code>@angular/cli</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="58c0978f65"><img src="https://img.shields.io/badge/58c0978f6-feat-blue" alt="feat - 58c0978f6" /></a></td>
<td>add support for Node.js 26.0.0</td>
</tr>
<tr>
<td><a href="a5c7c0b5fd"><img src="https://img.shields.io/badge/a5c7c0b5f-fix-green" alt="fix - a5c7c0b5f" /></a></td>
<td>reflect new minimum supported Node version in ng.js</td>
</tr>
</tbody>
</table>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/angular/angular-cli/blob/main/CHANGELOG.md">@angular-devkit/build-angular's changelog</a>.</em></p>
<blockquote>
<h1>22.0.1 (2026-06-10)</h1>
<h3><code>@angular/cli</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="b54e9a549d">b54e9a549</a></td>
<td>fix</td>
<td>do not sort migrations of the same version alphabetically</td>
</tr>
<tr>
<td><a href="d333116123">d33311612</a></td>
<td>fix</td>
<td>fallback to local package.json for schematic detection on first run</td>
</tr>
<tr>
<td><a href="918102a937">918102a93</a></td>
<td>fix</td>
<td>isolate temporary package installation from parent pnpm workspace</td>
</tr>
<tr>
<td><a href="b048b5f4a8">b048b5f4a</a></td>
<td>fix</td>
<td>remove forceAuth and unscoped credential parsing</td>
</tr>
<tr>
<td><a href="2779340351">277934035</a></td>
<td>fix</td>
<td>validate registry option is a valid URL in ng add</td>
</tr>
<tr>
<td><a href="4510dae021">4510dae02</a></td>
<td>perf</td>
<td>optimize update schematic registry query counts by fetching package metadata lazily</td>
</tr>
</tbody>
</table>
<h3><code>@schematics/angular</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="c800122945">c80012294</a></td>
<td>fix</td>
<td>fix browserMode option mapping in refactor-jasmine-vitest</td>
</tr>
<tr>
<td><a href="a9b6bd9042">a9b6bd904</a></td>
<td>fix</td>
<td>safely comment out multiline statements in refactor-jasmine-vitest</td>
</tr>
<tr>
<td><a href="12199df00f">12199df00</a></td>
<td>fix</td>
<td>use null objects and callbacks in karma-to-vitest migration</td>
</tr>
</tbody>
</table>
<h3><code>@angular/build</code></h3>
<table>
<thead>
<tr>
<th>Commit</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="89d1be979f">89d1be979</a></td>
<td>fix</td>
<td>allow disabling Vitest isolation from builder</td>
</tr>
<tr>
<td><a href="d45b84be9a">d45b84be9</a></td>
<td>fix</td>
<td>exclude JSON imports from Vite dependency optimization</td>
</tr>
<tr>
<td><a href="e3cab4ddda">e3cab4ddd</a></td>
<td>fix</td>
<td>prevent concurrent stylesheet bundling esbuild context leaks</td>
</tr>
<tr>
<td><a href="bd413b0eb1">bd413b0eb</a></td>
<td>fix</td>
<td>restrict application builder output paths to output directory</td>
</tr>
</tbody>
</table>
<h1>22.0.0 (2026-06-03)</h1>
<h2>Breaking Changes</h2>
<h3></h3>
<ul>
<li>Node.js v20 is no longer supported. The minimum supported Node.js versions are now v22.22.0 and v24.13.1.</li>
<li>The <code>@angular-devkit/architect-cli</code> package is no longer available. The <code>architect</code> CLI tool has been moved to the <code>@angular-devkit/architect</code> package.</li>
<li>The experimental <code>@angular-devkit/build-angular:jest</code> and <code>@angular-devkit/build-angular:web-test-runner</code> builders have been removed.</li>
</ul>
<h3><code>@angular/build</code></h3>
<ul>
<li>The <code>@angular/build:dev-server (ng serve)</code> now assigns the highest priority to the <code>PORT</code> environment variable. This value will override any port configurations specified in <code>angular.json</code> or via the <code>--port</code> command-line flag. This includes the default port 4200.</li>
<li><code>istanbul-lib-instrument</code> is now an optional peer dependency.
Projects using karma with code coverage enabled will need to ensure that istanbul-lib-instrument is installed. Note: <code>ng update</code> will automatically add this dependency during the update process.</li>
</ul>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="5a64af9918"><code>5a64af9</code></a> release: cut the v22.0.1 release</li>
<li><a href="b54e9a549d"><code>b54e9a5</code></a> fix(<code>@angular/cli</code>): do not sort migrations of the same version alphabetically</li>
<li><a href="b048b5f4a8"><code>b048b5f</code></a> fix(<code>@angular/cli</code>): remove forceAuth and unscoped credential parsing</li>
<li><a href="3275b45559"><code>3275b45</code></a> test(<code>@angular/cli</code>): remove unscoped authentication test cases from registry t...</li>
<li><a href="da81e55123"><code>da81e55</code></a> build: update cross-repo angular dependencies</li>
<li><a href="56ac3484f1"><code>56ac348</code></a> build: lock file maintenance</li>
<li><a href="12199df00f"><code>12199df</code></a> fix(<code>@schematics/angular</code>): use null objects and callbacks in karma-to-vitest m...</li>
<li><a href="918102a937"><code>918102a</code></a> fix(<code>@angular/cli</code>): isolate temporary package installation from parent pnpm wo...</li>
<li><a href="e9b106e662"><code>e9b106e</code></a> build: update cross-repo angular dependencies</li>
<li><a href="e3cab4ddda"><code>e3cab4d</code></a> fix(<code>@angular/build</code>): prevent concurrent stylesheet bundling esbuild context l...</li>
<li>Additional commits viewable in <a href="https://github.com/angular/angular-cli/compare/v21.2.14...v22.0.1">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@angular-devkit/build-angular&package-manager=npm_and_yarn&previous-version=21.2.14&new-version=22.0.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

2026-06-11 06:44:45 +00:00

flutter

Dart 3.9 / Flutter 3.35 [first LLM release] (#2714 )

2025-08-14 12:26:24 -07:00

src

Update ng-flutter embedding example to Angular v17 (#2081 )

2023-11-08 10:44:27 -08:00

.gitignore

Update Angular embedding sample (#2147 )

2024-01-24 15:53:52 -06:00

angular.json

Update ng-flutter embedding example to Angular v17 (#2081 )

2023-11-08 10:44:27 -08:00

package.json

Bump @angular-devkit/build-angular from 21.2.14 to 22.0.1 in /web_embedding/ng-flutter (#2853 )

2026-06-11 06:44:45 +00:00

README.md

Update ng-flutter embedding example to Angular v17 (#2081 )

2023-11-08 10:44:27 -08:00

tsconfig.app.json

Publish web_embedding (#1777 )

2023-05-06 10:53:17 +10:00

tsconfig.json

Publish web_embedding (#1777 )

2023-05-06 10:53:17 +10:00

tsconfig.spec.json

Publish web_embedding (#1777 )

2023-05-06 10:53:17 +10:00

README.md

ng-flutter

This Angular project is a simple example of how Angular and Flutter web apps could be integrated, and have them interop.

Points of Interest

Angular

This repository is a quite standard Angular app. The following changes were made to be able to use (and interop) with a Flutter web application:

package.json has a custom prebuild script that builds the Flutter web app, so Angular can find it later.
flutter.js is added as a "scripts" entry in angular.json. Angular takes care of minimizing and injecting it as any other script.
The rest of the flutter app flutter/build/web/ is registered as an "assets" entry in angular.json, and moved to /flutter.
The ng-flutter component takes care of embedding Flutter web, and yielding control to Angular through an appLoaded EventEmitter. The object yielded by this emitter is a state controller exposed by flutter via a JS custom event!

Flutter

The embedded Flutter application lives in the flutter directory of this repo. That application is a standard web app, that doesn't need to be aware that it's going to be embedded in another framework.

Flutter uses new @staticInterop methods to allow certain Dart functions to be called from JavaScript.
Look at how createDartExport and broadcastAppEvent work together to make the _state controller of the Flutter app available to Angular!

How to build the app

Requirements

If you want to build and run this demo on your machine, you'll need a moderately recent version of Angular:

$ ng version

Angular CLI: 17.0.0
Node: 20.9.0
Package Manager: npm 10.1.0
OS: linux x64

And Flutter:

$ flutter --version

Flutter 3.13.9 • channel stable
Framework • revision d211f42860 (2 weeks ago) • 2023-10-25 13:42:25 -0700
Engine • revision 0545f8705d
Tools • Dart 3.1.5 • DevTools 2.25.0

Ensure npm, ng and flutter are present in your $PATH.

Building the app

This repository is a moderately standard Angular app. It integrates Flutter web by making it part of the Angular assets.

In order to build this app, first fetch its npm dependencies:

$ npm install

added 963 packages, and audited 964 packages in 17s

93 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Then run the build script. It'll take care of building Flutter automatically:

$ npm run build

> ng-flutter@0.0.0 prebuild

... Flutter web build output ...

Compiling lib/main.dart for the Web...

> ng-flutter@0.0.0 build
> ng build

... Angular build output ...

✔ Browser application bundle generation complete.
✔ Copying assets complete.
✔ Index html generation complete.

Local Angular development

Once you've reached this point, you should be able to work with your Angular application normally, for example to run a local web server:

$ npm run start

> ng-flutter@0.0.0 start
> ng serve

✔ Browser application bundle generation complete.

Initial Chunk Files   | Names         |  Raw Size
vendor.js             | vendor        |   4.38 MB | 

... Angular build output...

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **


✔ Compiled successfully.

Navigate to http://localhost:4200/. The application will automatically reload if you change any of its Angular source files.

Local Flutter web development

The Flutter app lives inside the flutter directory, and can be developed independently. Just do any changes on Flutter web as you'd normally do. It even includes a small web/index.html so you can see changes to your app without running the whole Angular setup.

Note

For now, Angular does not auto-detect changes to your Flutter web app, so once you're happy with your Flutter web app, make sure to call npm run build so everything rebuilds and gets placed into its correct location.

Deploying the app

After npm run build, you should have a deployable Angular + Flutter web app in the dist directory of this Angular project.

Your built app can can be deployed anywhere, but do check Firebase hosting for a super-easy deployment experience!

Troubleshooting

Flutter

Ensure your flutter app is properly rebuilt after any changes.

Run npm run build to re-build the Flutter app.

If you encounter error messages like:

Error: Can't resolve 'flutter/build/web/flutter.js' in '/my/checkout/of/ng-flutter'

You definitely need to run npm run build!

Reach out to the team(s)!

Have you had any problem not covered in this README? Do you want to see other embedding examples?

Let us know by creating an issue or opening a new pull request.

Thanks!