feat: write generate resource and some utils

[ErKeLost]

#1793

1. add output file print log
   

2. add writeBundle

3. prepare out dir logic move to rust side

   • create out_dir dir
   • copy public dir
   • filter resource.emitter === true

4. add rust side logger

5. add some toolkit utils

[changeset-bot]

⚠️ No Changeset found

Latest commit: ca51a28

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "farm-docs" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[fu050409]

wdyt to add a plugin driver hook to notify plugins about public resource copy? or just leave the plugins to resolve completed files itself?somtimes some elder projects may need users add some files to public dir so we cannot optimize these files for now

[ErKeLost]

Copying publicDir should be our internal behavior of the framework. If the user needs to perform other special operations, they can do so in the finish hook or the upcoming writeBundle hook.

[ErKeLost]

After the entire write is completed, we can provide users with a writeBundle hook to manipulate the output file or other files.

[fu050409]

i think maybe it's better to use pnpm bootstrap -v instead?

[ErKeLost]

The reason why I suggest using verbose is that in some special cases, such as the first run of farm, Rust build can be extremely slow. Many developers cannot see the real Rust compilation progress and come to ask me if it is stuck. This is also why I use inherit to prompt developers.

[ErKeLost]

can add another command, but I still feel that verbose is the user's first intuition.

[ErKeLost]

Outputting the output file size in the Rust hook causes the program to wait for all threads to finish executing before proceeding, even though multiple threads have been started. This leads to longer overall compilation times. In JavaScript, we could make this run asynchronously, but I wonder if there are any better solutions; otherwise, we'll have to implement it in JavaScript after all.

Wait for all threads to finish execution here.

    const startTime = performance.now();
    await compiler.compile();
    const elapsedTime = Math.floor(performance.now() - startTime);
    const persistentCacheText = persistentCache
      ? bold(PersistentCacheBrand)
      : '';

[wre232114]

add a config option like output.fileSize and move this if statement to rust compiler similar to minify or tree shake.