samples VS pkg

Element Embedding demo source code

Source: https://github.com/flutter/samples/tree/main/experimental/element_embedding_demo :)

For a complete overview of M3 in Flutter, check out the official Material 3 Demo.

I've tinkered around with the https://github.com/flutter/samples/tree/main/add_to_app/android_view repository. I deleted the content of the dart files and replaced it with just a scaffold and button that connects to my method channel. I wrote a simple plugin which extends FlutterPlugin and Activity Aware the handle the method channel. My main problem seems to be, that the GeneratedPluginRegistrant.java file does not contain any references to my Flutter plugin. pub get within the Flutter Module doesn't add my plugin.

Simple state management, aka pragmatic state management, is based on Provider+ChangeNotifier. It's well documented, and there's a code sample.

That "toolkit" is basically a pubspec.yaml with preconfigured dependencies not including a game engine and some sample code how to use Firebase, Admob, and some other google services.

So it's been 3 days, since I started understanding the new Navigator 2.0 thing, and belive they were worst 3 days I have ever had with flutter, anyways I took nearly all of the code from this official repo.

I can respond to (c.) - We just released a navigation sample app, which demonstrates some common navigation scenarios. We are also actively researching routing and navigation APIs and will share more on that soon.

I don't remember the details, and cannot find my notes on vercel/pkg. But looking at https://github.com/vercel/pkg right now I see the project has been deprecated in favour of single-executable-applications

> Standalone CLI — we haven’t worked on a standalone CLI for the new engine yet, but will absolutely have it before the v4.0 release.

This part is the most exciting to me. Given the rest of the release announcement, I'm assuming this means that it'll be built in Rust rather than embed Node. While I'm not a Rust zealot of anything, I'm very partial to not embedding Node. Particularly when it depends on using Vercel's now-abandoned pkg[1] tool.`

[1] https://github.com/vercel/pkg

The npm package called "pkg" seems to be the standard for packaging NodeJS applications

https://www.npmjs.com/package/pkg

Unfortunately you also need to bundle all your code into a single file for it to work, but you can use any bundler (webpack, parcel, etc) you want at least

Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment:

"The single executable application feature currently only supports running a single embedded script using the CommonJS module system."

https://nodejs.org/api/single-executable-applications.html

Should be an awesome game changer for node.js when the feature gets rounded out.

Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291

Yes, you can. Check out pkg for a fun option, which can package up your project and Node.js into a single executable.

Further, you could experiment with the pkg tool that allows you to package up Node JS, your source, and your dependencies into one single executable for easy distribution.

package the app using https://github.com/vercel/pkg and use a smaller base image like alpine, busybox or even scratch (if possible)

Check this thread: https://github.com/vercel/pkg/issues/1685