Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish release 3.1.4 to npm #549

Open
socsieng opened this issue Oct 14, 2024 · 7 comments
Open

Publish release 3.1.4 to npm #549

socsieng opened this issue Oct 14, 2024 · 7 comments
Labels
wontfix This will not be worked on

Comments

@socsieng
Copy link
Contributor

Release 3.1.4 has been created, however, it hasn't been published to npm yet. Is there anything special, or any additional processes required in order to publish to npm?

@conico974
Copy link
Contributor

This is published to npm, but the name has changed https://www.npmjs.com/package/@opennextjs/aws

I'll keep this open for now so that other people can see it

@conico974 conico974 added the wontfix This will not be worked on label Oct 14, 2024
@socsieng
Copy link
Contributor Author

socsieng commented Oct 15, 2024

For anyone else who is using with SST, the following can be used until SST is updated to include: sst/sst#3994

new sst.aws.Nextjs("nextjs", {
  buildCommand: "npx @opennextjs/aws build",
  // ...
});

@MisterJimson
Copy link

Hmm will this break sstv2? We are passing the version like:

  const site = new NextjsSite(stack, 'dashboard-beta', {
    path: 'packages/dashboard',
    customDomain: customDomain,
    bind: getDefaultFunctionBindings(app),
    permissions: getDefaultFunctionPermissions(app),
    openNextVersion: '3.0.8',

@conico974
Copy link
Contributor

@MisterJimson Exact same fix as for V3

buildCommand: "nxp @opennextjs/[email protected] build"

There is a PR for this in SST v2, haven't checked if it has been merged or not

@MisterJimson
Copy link

And we would remove openNextVersion?

@conico974
Copy link
Contributor

It doesn't matter because openNextVersion will be overrided by the custom buildCommand. But it's probably better to remove it to avoid confusion

@niklaswallerstedt
Copy link

Here's the PR sst/sst#3873

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants