Skip to content

Update flags package json #62

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

Merged
merged 8 commits into from
Feb 14, 2025
Merged

Update flags package json #62

merged 8 commits into from
Feb 14, 2025

Conversation

AAorris
Copy link
Contributor

@AAorris AAorris commented Feb 11, 2025

Primary changes:

  • update tsup.config.js entry to drop the /index suffix.

Additional changes:

  • Use the same addressing in package.json
  • Use clean:true for tsup to drop the rimraf dependency
  • Mark node: imports as external instead of bundling them

@AAorris AAorris requested a review from a team February 11, 2025 16:38
@AAorris AAorris self-assigned this Feb 11, 2025
Copy link

vercel bot commented Feb 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
flags-sdk-snippets ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 14, 2025 7:44am
summer-sale ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 14, 2025 7:44am

Copy link

socket-security bot commented Feb 11, 2025

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@arethetypeswrong/[email protected] Transitive: environment, filesystem, network, shell, unsafe +52 31.5 MB andrewbranch
npm/[email protected] 🔁 npm/[email protected] None 0 238 kB react-bot

View full report↗︎

@@ -27,20 +27,20 @@
"require": "./dist/index.cjs"
},
"./next": {
"import": "./dist/next/index.js",
"require": "./dist/next/index.cjs"
"import": "./dist/next.js",
Copy link
Contributor

Choose a reason for hiding this comment

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

I think I've ran into issues when doing this in the past, either for exports or typesVersions, especially when importing this package.

Did you test it with a snapshot release?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've been iterating on the examples so far, but once they're passing, I'm looking to test a snapshot on an example ensuring it has legacy module resolution (moduleResolution: node)

@AAorris
Copy link
Contributor Author

AAorris commented Feb 12, 2025

Tested using https://arethetypeswrong.github.io/ (pnpm pack)

image

And on a preview deployment of our docs

Copy link
Collaborator

@dferber90 dferber90 left a comment

Choose a reason for hiding this comment

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

Looks good, thank you! I'd make this a patch instead of a minor as functionality has not changed.

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