Skip to content

feat: introduce @noaignite/next-klaviyo package - #801

Open
adamsoderstrom wants to merge 1 commit into
mainfrom
feature/next-klaviyo
Open

feat: introduce @noaignite/next-klaviyo package#801
adamsoderstrom wants to merge 1 commit into
mainfrom
feature/next-klaviyo

Conversation

@adamsoderstrom

Copy link
Copy Markdown
Member

No description provided.

@vercel

vercel Bot commented Jul 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 2, 2026 9:38am

Request Review

@changeset-bot

changeset-bot Bot commented Jul 2, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: ff7ed1d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@noaignite/next-klaviyo Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

}
}

export {}

@maeertin maeertin Jul 2, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

question: What does this do? Is it to disable automatic exports? Perhaps nice to add a simple explanation :)

// Disable automatic export
export {}

Comment on lines +1 to +4
export { klaviyo } from './klaviyo'
export { KlaviyoObject } from './KlaviyoObject'
export { KlaviyoScript } from './KlaviyoScript'
export type { KlaviyoScriptProps } from './KlaviyoScript'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

question: Why not just export *?

"default": "./src/index.ts"
}
},
"types": "./src/index.ts",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

question: is this needed? I was in the understanding that the exports field is enough :)

Comment on lines +30 to +33
"files": [
"src",
"dist"
],

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

question: Do we need/want to publish both src & dist?

Comment on lines +23 to +28
"exports": {
".": {
"types": "./src/index.ts",
"default": "./src/index.ts"
}
},

@maeertin maeertin Jul 2, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

question: What's the build script for if we point to src and not dist? Probably some faulty wiring here :)

"react": "^18.0.0 || ^19.0.0"
},
"engines": {
"node": ">=20.0.0"

@maeertin maeertin Jul 2, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

todo(non-blocking): We should probably raise this to at least version 22 which is actively maintained :)

@maeertin maeertin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Great work @adamsoderstrom 🥳 Left you some questions/todos. Resolve them and merge when you feel ready.

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.

3 participants