rlidwka

sinopia

JavaScript2014–2018

rlidwka / sinopia

sinopia

Private npm repository server

Systems & Infrastructure

Explore on GitHub Read Hacker News discussions

7Distinct people

8Mentions

0Explicit recommenders

5.5KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Private npm repository server

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2014-02-27 02:52:31 UTC to 2018-05-29 14:06:46 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	2	1	1
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	2	0	2
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	1	0	1
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	0	0	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	3	0	3

What Hacker News says

8 sources

jasonjayr·May 29, 2018

Just to save other users some time, it seems like sinopia is no longer maintained, and doesn't work on Node 8 https://github.com/rlidwka/sinopia/issues/456 Verdaccio, mentioned in a sibling comment seems to be the recommended replacement ... https://github.com/verdaccio/verdaccio

In NPM proxy users receiving ERR 418 I'm a teapot

madeofpalk·May 29, 2018

Sinopia was used at a previous job https://github.com/rlidwka/sinopia

In NPM proxy users receiving ERR 418 I'm a teapot

TheAceOfHearts·Mar 30, 2018

Clickbait. At least propose what it is that you think needs to be done to address this so-called chaos. Worth noting that ES2017 added String.prototype.padStart and String.prototype.padEnd. The whole left-pad thing is blown out of proportion. Second, you shouldn't be relying on npm for deployments. You dig your own grave. If package deletion is a concern, then host a mirror with something like Nexus [0], or pay for a service [1] [2] to do it for you. Over the years there have been a few local npm mirror tools [3], but I don't think any of em have really caught much traction. There's also the option of bundling each release. For that you can use a tool such as Webpack [4], or take it one step further and generate a single binary using something like pkg [5]. Developers also have the option of forking their dependency graph and updating ref

Read the rest

erences in package.json. Sooner or later you'll start to find bugs in your dependencies and have to fix them. It's your responsibility, you own all that code. Don't be afraid of maintaining your own fork. If you find a critical issue you'll probably need to be able to deploy your update without depending on a third-party anyway. This is fairly common in other ecosystems. Heck, you can also just check in your node_modules folder into version control. Don't get me wrong, npm certainly has its fair share of problems, and historically they haven't had the best defaults... But there's usually ways to work around the issues, and they're gradually working towards improving things. It's the developer's responsibility to handle their ecosystem's problems, which is also nothing new in the world of software development. [0] https://www.sonatype.com/download-oss-sonatype [1] https://jfrog.com/artifactory/ [2] https://inedo.com/proget [3] https://github.com/rlidwka/sinopia [4] https://webpack.js.org/ [5] https://github.com/zeit/pkg

In Time for developers to address the chaos of Node.js and NPM

TheAceOfHearts·Jan 28, 2016

We have npm as our single source of truth, although you could host your own npm, or use a tool like sinopia [0] which makes pretty reasonable tradeoffs while being usable. Instead of asking you to replicate all of npm, it just keeps local copies of your packages, and if a package isn't found it'll hit npm. [0] https://github.com/rlidwka/sinopia

In GitHub Outage

Gigablah·Nov 28, 2015

If npm speed or reliability is an issue you could also try a local registry cache: https://github.com/rlidwka/sinopia

In Why we stopped vendoring our npm dependencies

lobster_johnson·Apr 14, 2015

Sinopia [1] lets you run a private NPM repositroy. It can also act as a cache for the official npmjs.com repository. [1] https://github.com/rlidwka/sinopia

In Npm Private Modules

hunvreus·Aug 29, 2014Submission

Sinopia, Private Npm Repository Server

2 points · Open discussion

rlidwka·Feb 27, 2014

I wonder how it relates to a few npm forks (https://github.com/rlidwka/yapm, https://github.com/visionmedia/npm) created earlier this year, especially to second one since @visionmedia didn't change its name... And what about alternate npm-compatible registries (https://github.com/mbrevoort/node-reggie, https://github.com/rlidwka/sinopia, https://github.com/cnpm/cnpmjs.org), not based on CouchDB? "npm" isn't only a product name anymore since it's used extremely widely, so this doesn't seem like a good thing to do.

In Response to Nodejitsu NPM Trademark