Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can't use `optimizePackageImports` because it causes rendering errors

Open
#166 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
nextjs, typescript
Domain
frontend, web-dev

Research direction

Reproduce the failure with optimizePackageImports in next.config.js, then inspect the enrichTweet import used by CustomTweet in src/components/ui/blog/mdx/tweet/custom-tweet.tsx. Trace how the react-tweet exports are handled by Next.js package optimization; done means the page renders successfully with this configuration and no longer reports that enrichTweet is not a function.

Written by the indexing model from the issue text.

Description

If I add optimizePackageImports: ['react-tweet'], to my next.config.js it will cause the following error, breaking the page rendering

Error: (0 , _barrel_optimize_names_QuotedTweet_TweetActions_TweetBody_TweetContainer_TweetHeader_TweetInReplyTo_TweetInfo_TweetMedia_enrichTweet_react_tweet__WEBPACK_IMPORTED_MODULE_1__.enrichTweet) is not a function
at CustomTweet (webpack-internal:///(rsc)/./src/components/ui/blog/mdx/tweet/custom-tweet.tsx:11:208)
at eD (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:359300)
at e (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:365057)
at e8 (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:365554)
at e8 (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:365706)
at ta (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:371259)
at ti (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:371973)
at Timeout._onTimeout (/Users/jahir/dev/jahir/website/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.dev.js:35:360498)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7)
Dominant language
TypeScript
Stars
1.9k
Forks
119
Avg merge
6m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/react-tweet

All issues in vercel/react-tweet

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.