惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

I
InfoQ
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
B
Blog
罗磊的独立博客
GbyAI
GbyAI
博客园 - 三生石上(FineUI控件)
雷峰网
雷峰网
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Microsoft Security Blog
Microsoft Security Blog
宝玉的分享
宝玉的分享
The GitHub Blog
The GitHub Blog
人人都是产品经理
人人都是产品经理
博客园 - Franky
有赞技术团队
有赞技术团队
WordPress大学
WordPress大学
博客园 - 聂微东
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
Visual Studio Blog
MyScale Blog
MyScale Blog
Google DeepMind News
Google DeepMind News
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Reviving a Dead Plugin: How I Bring Back To Life the serv...
Oleksandr · 2026-06-15 · via DEV Community

Oleksandr

If you've been using the Serverless Framework to deploy static assets to S3, you've probably used serverless-s3-sync. It was the go-to plugin for syncing local directories to S3 buckets. Simple config, works after sls deploy, done.

Then, on January 1, 2026, the original author archived the repository. No more updates, no more security fixes. The most worrying thing - no more security fixes.

So I forked it, cleaned it up, and published it as serverless-s3-sync-v2.

Original Plugin Had a Problem

The original serverless-s3-sync worked, but its dependency tree was a historical artifact:

// Original dependencies (k1LoW/serverless-s3-sync)
{
  "@auth0/s3": "^1.0.0",
  "bluebird": "^3.5.1",
  "mime": "^2.4.0",
  "minimatch": "^3.0.4"
}

@auth0/s3 is itself a fork of the andrewrk/node-s3-client library, which hasn't been maintained for years. It's built on top of AWS SDK v2, which is also deprecated and has end-of-support on September 8, 2025. It handled the entire upload logic: directory scanning, MD5 diffing, multipart uploads, and the actual putObject calls.

bluebird was a Promise polyfill that made sense in 2015, when native Promises were slow or unreliable in Node.js. In 2026, it's pure dead weight.

The result: to sync a folder to S3, you were pulling in an unmaintained S3 client library that wrapped an unmaintained Promise library that wrapped an outdated AWS SDK. Four layers of abandoned code between you and a simple PutObject API call.

The Fork: What Changed

  1. Replaced @auth0/s3 + bluebird with direct AWS SDK v3

The most significant change. Instead of delegating to a middleware library, the fork talks directly to @aws-sdk/client-s3:

// Before (via @auth0/s3 abstraction)
const client = s3.createClient({ s3Options: awsOptions });
const uploader = client.uploadDir({ localDir, s3Params: { Bucket, Prefix } });

// After (direct AWS SDK v3)
const { S3Client, PutObjectCommand, ListObjectsV2Command, DeleteObjectsCommand } = require('@aws-sdk/client-s3');
const client = new S3Client(awsOptions);
await client.send(new PutObjectCommand({ Bucket, Key, Body, ContentType, ...params }));

AWS SDK v3 is modular — you import only what you need. No more pulling in the entire SDK.

  1. Rewrote sync logic with native async/await

bluebird is gone. All async operations use native Promise and async/await. The Node.js built-in crypto module handles MD5 hashing for ETag comparison:

const crypto = require('crypto');

function computeMD5(filePath) {
  return new Promise((resolve, reject) => {
    const hash = crypto.createHash('md5');
    const stream = fs.createReadStream(filePath);
    stream.on('data', chunk => hash.update(chunk));
    stream.on('end', () => resolve(hash.digest('hex')));
    stream.on('error', reject);
  });
}

  1. Node.js ≥ 20 requirement

The fork sets "node": ">=20" in engines. This enables native test runner (node --test), native fetch, and all modern async primitives without polyfills.

  1. Updated mime and minimatch

mime upgraded from v2 to v4 (ESM-aware, smaller, maintained)
minimatch upgraded from v3 to v10

  1. Added ESLint with standard config

The original repo lacks adding a consistent code style enforced via a linter. For linting JavaScript code, I added standard. For now, the standard hasn't been updated for 2 years, and I hope it will be brought back to life soon.

  1. Native Node.js test runner

Tests migrated from no tests to node --test, removing the need for a separate test framework dependency. A lot of unit tests were added to confirm the stability of the code.

Migration from the Original

If you're already using serverless-s3-sync, migration is two steps:

  1. Swap the package:
npm uninstall serverless-s3-sync
npm install --save serverless-s3-sync-v2

  1. Update serverless.yml:
plugins:
  - serverless-s3-sync-v2  # was: serverless-s3-sync

Your existing custom.s3Sync configuration stays exactly the same. All options are preserved:

  • bucketName / bucketNameKey
  • bucketPrefix
  • localDir
  • deleteRemoved
  • acl
  • params (per-file headers like CacheControl)
  • bucketTags
  • enabled (conditional sync rules)
  • --nos3sync CLI flag
  • Custom hooks
  • Offline mode via serverless-s3-local

Links

npm: serverless-s3-sync-v2
GitHub: AlexHladin/serverless-s3-sync
Original (archived): k1LoW/serverless-s3-sync

If this saved you from a supply chain dependency nightmare, give it a ⭐ on GitHub. PRs and issues welcome.