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

logseq-emoji-picker doesn't build: @parcel/core: Failed to resolve '@joeattardi/emoji-button' from './index.ts'

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
build-system

Research direction

Start in logseq-emoji-picker/index.ts at the import reported by Parcel, then run npm install && npm run build to reproduce the failure. Check the project's dependency configuration and verify that the declared package can be resolved; done means the sample builds successfully without the reported Parcel error.

Written by the indexing model from the issue text.

Description

npm install && npm run build
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility

added 181 packages, and audited 182 packages in 3s

72 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

> logseq-emoji-picker@0.0.1 build
> parcel build --public-url . --no-source-maps index.html

🚨 Build failed.

@parcel/core: Failed to resolve '@joeattardi/emoji-button' from './index.ts'

  /home/dieter/code/logseq-plugin-samples/logseq-emoji-picker/index.ts:2:29
    1 | import '@logseq/libs'
  > 2 | import { EmojiButton } from '@joeattardi/emoji-button'
  >   |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^
    3 | 
    4 | /**

Dominant language
CSS
Stars
383
Forks
97
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 logseq/logseq-plugin-samples

All issues in logseq/logseq-plugin-samples

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.