Description

Add name property for asset type bundle. The PR can solve the problem for #3028.

Additional context

It can solve the #3026 and other similar problem too. With the asset name, everyone can generate custom manifest format for need. eg the old manifest format

export default {
  root: './src',
  build: {
    manifest: false,
    rollupOptions: {
      input: './src/entry/main.js'
    }
  },
  plugins: [
    {
      async generateBundle(options, bundle) {
        let manifest = {}
        for (const file in bundle) {
          const chunk = bundle[file]
          if (chunk.type === 'chunk') {
            if (chunk.isEntry) {
              manifest[chunk.name + '.js'] = {
                file: chunk.fileName,
                imports: chunk.imports
              }
            }
          } else if (chunk.name) {
            manifest[chunk.name] = { file: chunk.fileName }
          }
        }
        this.emitFile({
          fileName: 'manifest.json',
          type: 'asset',
          source: JSON.stringify(manifest, null, 2)
        })
      }
    }
  ]
}

The manifest.json should looks like

{
  "images/favicon.svg": {
    "file": "assets/favicon.17e50649.svg"
  },
  "images/demo.png": {
    "file": "assets/demo.098465ec.png"
  },
  "font/font.ttf": {
    "file": "assets/font.a0d06a46.ttf"
  },
  "main.js": {
    "file": "assets/main.c58b35ad.js",
    "imports": []
  },
  "main.css": {
    "file": "assets/main.babcb300.css"
  }
}

Then can get the assets/demo.098465ec.png by images/demo.png for backend.

src
├── entry
│   └── main.js
├── font
│   └── font.ttf
├── images
│   ├── demo.png
│   └── favicon.svg
└── style
    └── style.css

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.