[Feature] Not need to set the publicPath in development when using manifest

[fz6m]

Clear and concise description of the problem

Currently, setting the publicPath is forced in development, IMO it is redundant and unnecessary.

If we know a URL, we can infer its publicPath.

For example:

  remotes: {
    mf_remote: 'mf_remote@http://localhost:9527/mf-manifest.json',
    // inferred as `http://localhost:9527/`
  }

If the consumer side finds that the publicPath does not start with https?:// or // , it should first try to fetch the possible URL ( use http://localhost:9527/ as publicPath ) and check response, if no response, then fallback try to fetch http://${current_project_host}:${current_project_port}/ (the end with / is publicPath ) .

Suggested solution

No Response

Alternative

No response

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[ScriptedAlchemy]

Yeah this is something I already have planned and spoke to @2heal1 about. Will try to send a PR this week

[zhoushaw]

Thank you for your advice, I think this might be a good idea, and we'll try to see how this works

[ScriptedAlchemy]

PR has merged, should release soon

[ScriptedAlchemy]

@fz6m this should be released now