feat(dev): add BrowserMeta file for @remix-run/dev

[19Qingfeng]

Closes: #6416

• Docs
• Tests

I opened up my may machine and ran this script:

1. Create a playgroud project, modify metafile: true in remix.config.js, and run npm run build to compile remix-run project.
   After that, look at debugDirectory(public/.debugger) to get the js-metafile.json file.

2. Create a playgroud project, modify metafile: true and debugDirectory: ".debugger" in remix.config.js, and run npm run build to compile remix-run project.
   After that, look at debugDirectory(.debugger) to get the js-metafile.json file.

3. Create a playground project, execute remix build --metafile,then you will get js-metafile.json.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 488763b

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[remix-cla-bot]

Hi @19Qingfeng,

Welcome, and thank you for contributing to Remix!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected].

Thanks!

- The Remix team

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

[pcattori]

@19Qingfeng thank you for the PR!

I think the direction we want to go in is to have a --metafile option that produces the metafile(s) into a dedicated directory.
Maybe default to .debug/ and configurable with debugDirectory option in remix.config.js or something like that.

[19Qingfeng]

@19Qingfeng thank you for the PR!

I think the direction we want to go in is to have a --metafile option that produces the metafile(s) into a dedicated directory. Maybe default to .debug/ and configurable with debugDirectory option in remix.config.js or something like that.

Okay, I will refer to your feedback to modify the parameter name and generation location. I will resubmit it later. Thank you.

[19Qingfeng]

@19Qingfeng thank you for the PR!

I think the direction we want to go in is to have a --metafile option that produces the metafile(s) into a dedicated directory. Maybe default to .debug/ and configurable with debugDirectory option in remix.config.js or something like that.

@pcattori hello,pcattori.Now, this time with the metafile and debugDirectory parameters, I will update the test description later.

[19Qingfeng]

@pcattori hi, i updated the code and synchronized the description, please check the changes.

[19Qingfeng]

@pcattori Can you provide some feedback? Perhaps I can make further modifications

[Doelfke]

What's the status of this?

[19Qingfeng]

What's the status of this?

I'm not sure what the remix team is thinking right now. If I have an idea, Maybe I can resolve the conflict and modify the code.

[pcattori]

Superceded by #6772