Skip to content

Conversation

orinokai
Copy link

@orinokai orinokai commented Oct 23, 2024

Summary

Update to use new package name for our Next.js Adapter, which is moving to the @opennextjs scope.

To do

orinokai and others added 2 commits October 23, 2024 13:27
We're not calling it a "runtime" anymore.

Plus this was super leaky anyway, assuming that any auto-installed build plugin is a "runtime".
pluginsRecommended: string[] = [],
) => {
const nextRuntime = '@netlify/plugin-nextjs'
const nextRuntime = '@opennextjs/netlify'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This took me a while to understand — this is part of 'init' i.e. used in ntl init and related scenarios, and its purpose is to literally auto-install the plugin on the site via the Netlify API if it isn't already installed and we've detected that it should be. So it's OK to just update this name and not "handle" the old name in any way.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... although, wait, isn't there a case like this?

  1. next.js site exists today with @netlify/plugin-nextjs installed
  2. we release this cli change
  3. user clones their repo, runs ntl init, it checks and finds that @opennextjs/netlify is not auto-installed (even though @netlify/plugin-nextjs is) and auto-installs @opennextjs/netlify.
  4. user has both plugins installed

@serhalp
Copy link
Member

serhalp commented Feb 28, 2025

No longer planned

@serhalp serhalp closed this Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants