Move @lazarv/react-server-router to be part of the core framework package

[lazarv]

Description

As it turns out providing file-based routing as a separate package is causing more confusion than adds value of flexibility. It will be also easier to communicate usage and brings common expectations more into picture. The framework will still keep the current feature set! The developer just don't need to install another package to use the file-based router. By not specifying the entry point of an app, the file-based router will get resolved as the entry point, exactly the same way as it is right now.

Suggested solution

Move @lazarv/react-server-router content into the @lazarv/react-server package. Keep the old name as a module alias so it's still overridable if needed.

As the router will be part of the core framework package, there's no more need to check if the router is installed for the user or not when not using an entry point.

Alternative

No response

Additional context

No response

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[github-actions[bot]]

This issue has been locked since it has been closed for more than 30 days.

If you have found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest version of @lazarv/react-server. If you have any other comments you should create a new discussion.