Why I switched from #NVM to #FNM?

https://eshlox.net/why-i-switched-from-nvm-to-fnm

Anyway, this was somehow due to #Node.js being upgraded or something like that - which taught me to pin/recommend a specific node version on my projects. Not really the type of thing I've encountered with #Python before to think about it too much.

This also taught me, perhaps the importance of installing an LTS version of Node. This also led me to discover #nvm, which is a super neat way of managing multiple Node.js versions on a single system.

I've documented in my Wiki how I set nvm up.

https://github.com/irfanhakim-as/linux-wiki/blob/master/topics/nodejs.md

RE: https://sakurajima.social/notes/a47ygtfrtd

People joke about installing Python environments (https://xkcd.com/1987/), but I'm looking at #Typescript and... am I misunderstanding, but `sudo apt install npm` (on #Ubuntu2204) gives me a #node version (12.22) that isn't compatible with installing the typescript package (EBADENGINE required: node >=14.17). So I should install latest node using #nvm, which installs via curl of a script which git clones its own repo to my ~/.npm, does this sounds right so far? #newb #seekingAdvice

After programming a good 2 months in #python finally found the tool #poetry which is quite similar to how #nodejs bundles libraries into a directory either locally or globally in the cache directory.

I have tried the other tools from #pyenv to #venv and/or #virtualenv. Where I thought they were used to deal with library dependency management only to realize that they are more like #nvm.

I did use #conda for some time, though preferred a python only solution. I do realize that poetry won't resolve all issues and might need to look into to containerization later on, though for the time period it looks like a good solution.

Soso, zur Einführung hat der neue Verkehrsverbund in Unterfranken (#NVM) nun ein bis September befristetes verbundweites Tagesticket im Angebot. Für 9€ ein ziemlich guter Deal.

Vorschlag: Nehmt den Preis mal zwei, verstetigt das für den gesamten Verbund und reduziert eure ~470 Tarifzonen auf sieben: eine pro Landkreis.

Führt dann noch ein Tagesticket für 8€ innerhalb der jeweiligen Zone ein und es bestünde die Gefahr eines verständlichen Tarifsystems, das die Leute auch nutzen wollen.

I need to investigate which is the best and simpler (with no o little external packages) to use #emacs with things like #pyenv , #rbenv or #nvm. All of those configure the environment in a way that emacs is not expecting

Sehe ich das richtig, dass der zum ersten Januar gestartete Verkehrsvehrsbund #NVM – #Nahverkehr Mainfranken – mit rund 470 (VIERHUNDERTSIEBZIG!!!) einzelnen Tarifzonen daher kommt?!?

Habt ihr sie nicht mehr alle?!? Das ist rund das Dreifache der Zonen die z.B. der HVV hat und auch das ist viel zu viel!

Nur die Städte Schweinfurt und Würzburg machen es richtig: 1 Zone + Kurzstreckentickets! #öpnv

Using #nvm to manage #node versions for your projects? With Flox you can manage Node.js version along with all of your other dependencies (PostreSQL, Python, Rust, etc) with one tool.

Learn more: https://flox.dev/docs/tutorials/migrations/nvm/

Usando o Mastodon com a versão mais recente do NVM
@fediadminbr@lemmy.eco.br

Se você usa o NVM para gerenciar a versão do NodeJS em sua instalação do Mastodon (não-Docker), deve achar um saco ficar editando arquivo de serviço a cada versão nova.

Mas há uma solução mais prática e automática:

1) Edite seu arquivo `mastodon-streaming@.service`
2) Inclua a seguinte linha:

`Environment="NODE_VERSION=node"`

3) Substitua a linha `ExecStart` por:

`ExecStart=/home/mastodon/.nvm/nvm-exec node ./streaming`

4) Salve, execute `systemctl daemon-reload` e reinicie o serviço `mastodon-streaming@*`

Deixando `node` em `NODE_VERSION` vai usar a versão configurada como padrão na sua instalação do NVM.

Sempre que atualizar a versão do NodeJS pelo NVM, basta reiniciar o serviço `mastodon-streaming@*` para começar a usá-la.

PS.: o Lemmy adicionou uma barra invertida onde não devia, como antes de underline e asterisco. Veja o post original para não quebrar sua instalação.

@fediadminbr@a.gup.pe

Using #nvm in your #javascript project? Have a .nvmrc committed to source control? tired of having to update the node-version in your #CI workflows?

TIL: #Github Actions actions/setup-node action lets you point to your .nvmrc file

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version-file: .nvmrc
          cache: 'npm'
      - run: npm t

I've switched from #asdf https://asdf-vm.com/ to #mise https://github.com/jdx/mise to manage my different #node and #python versions and it's awesome. If you're still using #asdf you should definitively switch to #mise, it's way faster and mostly compatible with asdf (using .tools-versions).
If you're still using #pyenv, #nvm or stuff like that to manage your envs, you should give mise a try!

5 #Node Version Managers Compared – Which is Right for You?
#NVM is perhaps the best known, but maybe #N, #FNM, #Volta, or even #pnpm could suit you better? #NodeJS
https://pavel-romanov.com/5-node-version-managers-compared-which-is-right-for-you

#retrogames #history

Some highlights from my recent trip to the National #VideoGame #Museum #NVM in #Dallas #Texas.

1. #Atari Space Race prototype #arcade cabinet
2. Ralph Baers original prototype #Pong video game machine
3 #Microvision, the first handheld game console that used interchangeable cartridges
4. A rainbow #atari2600

https://nvmusa.org/

𝗡𝗩𝗠 𝘀𝗼𝗺𝗯𝗲𝗿 𝗼𝘃𝗲𝗿 𝘄𝗼𝗻𝗶𝗻𝗴𝗺𝗮𝗿𝗸𝘁: 𝘁𝗲 𝘃𝗲𝗲𝗹 𝘀𝘁𝗮𝗿𝘁𝗲𝗿𝘀, 𝘁𝗲 𝘄𝗲𝗶𝗻𝗶𝗴 𝗱𝗼𝗼𝗿𝘀𝘁𝗿𝗼𝗺𝗲𝗿𝘀

De woningmarkt is en blijft krap. Er staan weinig woningen te koop, de prijzen zijn weer gestegen en de zogeheten doorstromers kopen eerst een nieuw huis voor ze hun oude woning in de verkoop zetten. Omdat geld lenen relatief gunstig is, zijn er ook veel starters actief.

https://www.rtlnieuws.nl/economie/life/artikel/5444644/nvm-cijfers-woningmarkt-veel-starters-weinig-doorstromers-prijzen

I got whipped today, trying to use cloud-init to spin up an #EC2 instance and install #nvm. I was really feeling the dumb until I had someone pair with me, and they were hitting the same issues as me.

There’s even an Ansible role for it, that’s not really a smooth operation either.

𝗡𝗩𝗠: 𝗺𝗲𝗲𝗿 𝗵𝘂𝗶𝘇𝗲𝗻 𝘃𝗲𝗿𝗸𝗼𝗰𝗵𝘁, 𝗽𝗿𝗶𝗷𝘇𝗲𝗻 𝗼𝗺𝗵𝗼𝗼𝗴

Wie eind 2023 een bestaande woning kocht, betaalde daar 5,3 procent meer voor dan een jaar eerder. De doorsnee verkoopprijs was 434.000 euro. De prijs van koopwoningen steeg het hardst in Noord-Limburg.

https://www.rtlnieuws.nl/economie/artikel/5428702/minder-woningen-te-koop-duurder

Today I got some time to find out why my #zsh takes a noticeably long time to start. The offender was #nvm. As I removed it, the time got down from 450ms to 60ms.

To time startup of zsh vs bash:

$ for i in $(seq 1 10); do /usr/bin/time bash -i -c exit; done

$ for i in $(seq 1 10); do /usr/bin/time zsh -i -c exit; done

To find how long each plugin takes at startup, add `zmodload zsh/zprof` at the top of `~/.zshrc` and `zprof` at the bottom.

as I understand it, #nodejs #nvm is equivalent to #pyenv

is this understanding correct ?