8 posts tagged with "nodejs"

Never thought you'd need to handle database migrations in Node.js? Me neither. Anyway, here’s one way to do it. Oh, and I think Node.js blog posts need emojis, right? 💯💡

Last month Microsoft introduced a new release of the Microsoft Graph Developer Proxy. The latest release introduces support for monitoring specific processes, a new plugin allowing testing against rate limiting supported APIs and provides a new OData paging guidance.

There are a few package managers for Node.js projects and some of them provide advantages over others. Currently, we use yarn and we face some challenges, that may be solved by migrating to pnpm.

A few years ago we switched projects from npm to yarn and in the near future, we will move to pnpm for several reasons (which will be explained in another blog post). Often we have to adapt the scripts in package.json to use the correct package manager.

Sometimes folders like node_modules consume too much space and then a small cleanup may be needed.

Am Dienstag den 30.06.2015 trifft sich die node.js Usergroup Mannheim wieder bei uns. Anmeldungen bitte auf der entsprechenden meetup.com Seite vornehmen. Danke!

Am Donnerstag den 26.02.2015 trifft sich die node.js Usergroup Mannheim bei uns. Thema des Abends sind REST APIs mit einem entsprechenden Vortrag dazu. Damit wir besser planen können bitte auf der entsprechenden meetup.com Seite anmelden. Danke!

Recently we were in the need to create (and host) an own npm module. Setting up a private repository with sinopia seemed like a bit too much work for hosting just a single npm package. So I decided to use the built-in functionality of npm to directly refer to a git repository in the package.json file. This worked fine on "my machine" but failed on my co-workers machine. It turned out that we were both using the same version of nodejs and npm but we were running different versions of git. I had a recent version of git running. My co-worker's git version was pretty old (1.7.x). I advised that we should upgrade git any try again. And guess what, after the upgrade npm install worked perfectly fine.