Skip to content

☂️ Umbrella: List of potential features / changes for a major version #2047

@amannn

Description

@amannn

This is a list of ideas for API changes that we could potentially introduce in a major version:

  • Replace tsc with rollup-plugin-dts in build #2049 (ideally this is non-breaking, but to be safe we could schedule it for a major version)
  • Investigate if we could remove t.rich and t.markup in favor of a universal t function that works for all cases.
  • Investigate if we could get rid of t.raw. It leads users to toward bad patterns that might not work with future optimizations (see Improved type-safety for `t.raw()` and improved autocomplete. #2076 (comment) for details).
  • Fix casing getTimeZone (next-intl) vs Timezone (use-intl)
  • Consider making NextIntlClientProvider server-only (with IntlProvider being available on the client). The environment makes a difference here and it might be to easy to get wrong. In this case, we'd also move it to next-intl/server. Not sure if the benefit is big enough though.
  • Rename "middleware" in APIs to "proxy"
  • Should Link that changes a locale include nofollow by default? This could help search engines avoid indexing this link while allowing us to use a safe href before hydration. Search engines should pick up localized variants from alternate links or a sitemap.
  • Remove "node10" types support
  • Only a loose thought for now, but I wonder if it could be helpful to return routing config from request.ts instead of passing it to a factory function like createNavigation. Really not sure yet if it's worth it, but could be something to investigate.

No decision has been made on these so far, but if you have feedback about these points, please leave it here!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions