Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Android 17 is the first since 3.x to add new APIs without releasing to the AOSP(grapheneos.social ↗)
    263comments
  2. Cloudflare Quick Tunnels(cloudflare.com ↗)
    250comments
  3. Saving another 100TB of RAM(cloudflare.com ↗)
    44comments
  4. The Farnese letter(simonklee.dk ↗)
    5comments
  5. Xcode 27.1 Beta Release Notes(developer.apple.com ↗)
    68comments
  6. How to Write with an LLM(sockpuppet.org ↗)
    271comments
  7. Photon-Emission-Guided Laser Fault Injection Enables RP2350 Secure Debug(ledger.com ↗)
    54comments
  8. How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip(ieee.org ↗)
    58comments
  9. Show HN: Cactus Needle 3: 8-29MB automation models can match DeepSeek V4 Flash(cactuscompute.com ↗)
    78comments
  10. Cache-to-Cache: Direct Semantic Communication Between LLMs (2025)(arxiv.org ↗)
    12comments
  11. The first new cat species discovered in 100 years(nationalgeographic.com ↗)
    61comments
  12. OpenJev(openjev.com ↗)
    246comments
  13. Claude Code now reads AGENTS.md if there is no Claude.md(claude.com ↗)
    182comments
  14. Cyclomatic Complexity in C#(ndepend.com ↗)
    15comments
  15. Show HN: LiveWorld – Every 24/7 YouTube live camera on one globe(liveworld.info ↗)
    5comments
  16. Minimal Phone 2(minimalcompany.com ↗)
    177comments
  17. The Implications of Linguistic Illegibility for LLM Security(arxiv.org ↗)
    19comments
  18. Warez: The Infrastructure and Aesthetics of Piracy (2021)(archive.org ↗)
    25comments
  19. Alibaba open-sources AI model that can detect cancer and nearly 150 conditions(scmp.com ↗)
    4comments
  20. Two parallel neural ectoderm progenitors contribute to the developing brain(newscientist.com ↗)
    54comments
  21. C++26: Trivial infinite loops are no longer undefined behaviour(sandordargo.com ↗)
    201comments
  22. Column built an issuer processor from scratch(column.com ↗)
    5comments
  23. Inside ZCode: Silently uploading your Git history to the cloud(ferstar.org ↗)
    91comments
  24. How SpaceX streamlined the Raptor engine(construction-physics.com ↗)
    40comments
  25. LispBM is a concurrent Lisp for microcontrollers with message passing(lispbm.com ↗)
    1comments
  26. A search-and-inference database from scratch in pure Zig(antfly.io ↗)
    16comments
  27. I vibed a proof of Conway's conjecture(overreacted.io ↗)
    186comments
  28. Size-Specialized Memory Allocation(go.dev ↗)
    3comments
  29. North Korean nuclear test sets off years of earthquakes(science.org ↗)
    152comments
  30. From Geometry to Algebra and Back Again: 4000 Years of Papers (2023) [video](youtube.com ↗)
    discuss

Show HN: Sync your NPM packages to verdaccio with ease

1 pointsby 1y agogithub.com
0 comments
In everyday development, we sometimes need to develop in a highly secure environment. This leads to the existence of internal and external networks.

The internal network cannot use npm for dependency installation. Imagine if we added a new project on the external network each time and needed to synchronize it with the internal network for development—would we have to package the entire node_modules directory and transfer it to the internal network? This is clearly impractical.

The best approach is to set up Verdaccio on the internal network. Each time, we only need to synchronize our source code to the internal network. Therefore, managing dependencies between the internal and external networks becomes critical.

Common Issues with Verdaccio Usage

1. Manual publishing is cumbersome: Each package must be manually published to verdaccio using npm publish. When there are many packages, the workload is enormous, and the publication time is unpredictable.

2. verdaccio may not display packages that already exist, resulting in a poor user experience

3. Complex dependency relationships: Packages may have complex dependency relationships, and manual publishing is prone to omitting dependent packages

4. Repetitive work: Every project update requires manually republishing all related packages

5. Low efficiency: The entire process is time-consuming and labor-intensive, impacting development efficiency

Problems Solved by sptv-cli 1. Automated Synchronization: One-click automatic synchronization of external packages to internal Verdaccio, eliminating manual publishing

2. Intelligent Dependency Scanning: Automatically scans and identifies package dependencies, ensuring all dependent packages are synchronized

3. Batch Processing: Supports batch processing of multiple packages, greatly improving synchronization efficiency

4. Version Consistency: Ensures package versions in internal Verdaccio are completely consistent with external networks

5. Progress Visualization: Real-time display of synchronization progress, keeping users informed of operation status

6. Flexible Configuration: Supports multiple configuration options to adapt to different usage scenarios

SPTV-CLI allows you to focus solely on managing your packages.

A quiet thread, for now.Start the conversation on HN ↗