New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
corepack enable - command not found: nodejs 16 moved to 18.7 on apt update first time #1032
Comments
node v shows 'v18.7.0' |
SOLVED: must install the LTS version and not version 16. when using instead run for LTS corepack enable (success) When they released v18.7.0 they must have not included corepack |
Oops..forgot. If you already installed setup_16.x or apt-update has otherwise changed your system to nodejs v18.7.0 ####this will install v18.12.1 which DOES include corepack |
Looks like there is now a deprecation warning, from running the first script:
|
Fresh install Ubuntu 22.04-- following mastodon install from source instructions
Specifically requested nodejs v 16 (failed several prev wipe|clean installs trying to use v19)
curl -sL https://deb.nodesource.com/setup_16.x | bash -
during subsequent steps
apt update
upgraded nodejs to version 18.7
ran apt install -y on the whole set including nodejs no errors all went fine all success
next step corepack enable fails
'corepack: command not found'
without yarn, mastodon will not function
without corepack, yarn may not function correctly
did deep dive searches for help. During prev attempts with nodejs v19 I installed yarn and corepack using npm but final deployment of mastodon would not generate any user pages or content (admin pages worked tho) so tried again this time with a clean wipe fresh UBUNTU with strict nodejs version 16 requested and the apt update seems to have broken something as corepack is not included in standard install of version 18.7
Help------continue by installing npm, then using npm to install corepack and yarn?
Or stop and wait until someone figues out why corepack and yarn not included in 18.7 clean install
The text was updated successfully, but these errors were encountered: