[Bug]: Library name syntax

[natocTo]

System Info

System:
- OS: macOS 14.5
- CPU: (11) arm64 Apple M3 Pro
- Memory: 130.86 MB / 18.00 GB
- Shell: 5.9 - /bin/zsh

Binaries:
- Node: 20.15.1 - /opt/homebrew/bin/node
- Yarn: 1.22.22 - ~/Documents/GitHub/ui/node_modules/.bin/yarn
- npm: 10.2.3 - ~/Documents/GitHub/ui/node_modules/.bin/npm

Browsers:
- Chrome: 129.0.6668.89
- Safari: 17.5

Details

When library name is configured based on docs - https://rspack.dev/config/output#outputlibraryname

module.exports = {
  // …
  output: {
    library: {
      name: 'MyLibrary',
      export: 'default'
    },
  },
};

It fails on schema validation before build:

Invalid configuration object. Rspack has been initialized using a configuration object that does not match the API schema.
│ - Unrecognized key(s) in object: 'name', 'export' at "output.library"
│ [rspack-cli] [Error:   × Library name must be a string or string array. Common configuration options that specific library names are 'output.library[.name]', 'entr
│ y.xyz.library[.name]', 'ModuleFederationPlugin.name' and 'ModuleFederationPlugin.library[.name]'.
│ ] {
│   code: 'GenericFailure'
│ }

It works for "older" syntax, but it is "deprecated" - https://rspack.dev/config/output#outputlibraryexport-1

module.exports = {
  // …
  output: {
    library: 'MyLibrary',
    libraryExport: 'default'
  },
};

Reproduce link

No response

Reproduce Steps

1. use newer library name syntax
2. try build library

[natocTo]

I now see it works when "type" is also defined. 👍 So maybe just mention this in the documentation. Or somehow tune validation, it was not clear what is wrong.

---

Btw, I would not expect that migration from Webpack would be that "simple". Great work.