NotionX / NotionX/react-notion-x
Webpack build can't resolve p-queue or mem
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 645
- PR merge metrics
- No merged PRs in 30d
Description
Description
Webpack 4 builds throw can't resolve p-queue and mem in node_modules/notion-utils/build
Example repo (fork and run): https://replit.com/@nathanwaters3/Reactjs-Babel-Webpack-Boilerplate#src/App.js
In that Repl it only throws p-queue error but in local build it also throws mem "can't resolve" error.
Notion Test Page ID
In code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Webpack 4 build from the linked Replit example and inspect dependency resolution under node_modules/notion-utils/build. Check why p-queue and mem cannot be resolved; done means the build completes without either resolution error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- webpack
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100