i'm experiencing some problems in trying the examples
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 225
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
i'm experiencing some problems in trying the examples...
Would you be so kind in explaining how to use them?
(base) marco@pc01:~/webMatters$ git clone https://github.com/jaredly/local-first.git
Cloning into 'local-first'...
remote: Enumerating objects: 5882, done.
remote: Counting objects: 100% (5882/5882), done.
remote: Compressing objects: 100% (2182/2182), done.
remote: Total 5882 (delta 4092), reused 5347 (delta 3557), pack-reused 0
Receiving objects: 100% (5882/5882), 2.93 MiB | 6.27 MiB/s, done.
Resolving deltas: 100% (4092/4092), done.
(base) marco@pc01:~/webMatters/local-first$ yarn
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
(base) marco@pc01:~/webMatters/local-first/examples/quill-crdt$ yarn
yarn install v1.22.4
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > quill-cursors@3.0.2" has incorrect peer dependency "quill@>1.3.7".
warning " > quill-cursors@3.0.2" has unmet peer dependency "quill-delta@>4.2.1".
[4/4] Building fresh packages...
Done in 3.28s.
(base) marco@pc01:~/webMatters/local-first/examples/quill-crdt$ yarn add quill
yarn add v1.22.4
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > quill-cursors@3.0.2" has incorrect peer dependency "quill@>1.3.7".
warning " > quill-cursors@3.0.2" has unmet peer dependency "quill-delta@>4.2.1".
[4/4] Building fresh packages...
warning No license field
success Saved 1 new dependency.
info Direct dependencies
└─ quill@1.3.7
info All dependencies
└─ quill@1.3.7
Done in 1.47s.
(base) marco@pc01:~/webMatters/local-first/examples/quill-crdt$ yarn add quill-delta
yarn add v1.22.4
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > quill-cursors@3.0.2" has incorrect peer dependency "quill@>1.3.7".
[4/4] Building fresh packages...
success Saved lockfile.
warning No license field
success Saved 4 new dependencies.
info Direct dependencies
└─ quill-delta@4.2.2
info All dependencies
├─ fast-diff@1.2.0
├─ lodash.clonedeep@4.5.0
├─ lodash.isequal@4.5.0
└─ quill-delta@4.2.2
Done in 1.50s.
And then?
Contributor guide
No contributing guide indexed for this repository
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 reviewing the repository examples, especially examples/quill-crdt, and the setup sequence shown with yarn, quill, and quill-delta. Done means the examples have clear next-step usage instructions after installation, including how to run or open them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100