Installer warning if old node version
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- desktop
Research direction
Start by locating the installer entry point and checking how it detects or uses the installed Node.js version. Confirm the minimum supported version from the project’s current requirements, then make the installer warn users when their version is too old and suggest updating it.
Written by the indexing model from the issue text.
Description
From @mroeder
At first I installed the Lively Kernel Scripts App one somewhere in between state of "I have nothing" and "I have successfully installed it" with the App (meaning I had some version of Node.JS, git and lively-kernel-scripts installed already). After a problem-free installation of the app, I found out that the app was using my old lk-scripts and its repository to work with. Also the app did not seem to work - update workspace/PartsBin: nothing happened. So I uninstalled the app, uninstalled the lk-scripts I had before and gave it a second try.
Second successful installation and now it was using the workspace and PartsBin that should have been installed and use the first time as well. But still, the app did not work: None of the commands was working and so I was debugging again. Calling the lk script from the command line seemed to do the job. When I was doing it as root. So I checked for my Node.JS version - it was 0.6.x - and uninstalled that one, installed the latest one (0.8.x) and updated my node modules. Afterwards it worked like a charm.
Suggestion: Maybe the installer should warn you if you have an old Node.JS version and suggest updating it. I did not find a hint on what version is need anywhere :-/.
- Dominant language
- Objective-C
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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
- 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.
More from LivelyKernel/livelykernel-scripts.app
-
Is this expected?Open
Difficulty 4/5 3-5 days Newbie friendliness 15/100
LivelyKernel/livelykernel-scripts.app#4 · 4 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in LivelyKernel/livelykernel-scripts.app
Similar issues
-
React-Native Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-react-native#6822 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-2 days Newbie friendliness 78/100
getsentry/sentry-cocoa#9219 · 1 comment ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
DataDog/dd-sdk-ios#3255 · 1 comment ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
repowise-dev/repowise#2785 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100