Website Dependencies and Libraries Update

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

Website Dependencies and Libraries Update

Outdated dependencies — source of vulnerabilities and technical debt. Can't postpone updates until "accumulated" because larger version gap means more complex and risky upgrade.

Update strategy

Patch versions (1.2.3 → 1.2.4) — automatically via Dependabot/Renovate, no manual testing needed.

Minor versions (1.2.x → 1.3.0) — automatically with manual CHANGELOG check for breaking changes.

Major versions (1.x → 2.0) — separate task with full testing, often requires code changes.

npm/Node.js: audit and update

# Audit vulnerabilities
npm audit
npm audit --audit-level=high  # high/critical only

# Auto-fix minor vulnerabilities
npm audit fix

# List outdated packages
npm outdated

# Update single package
npm update react react-dom

# Update to next major version
npx npm-check-updates -u  # updates package.json
npm install               # installs updated versions

PHP/Composer: update

# List outdated packages
composer outdated

# Update within constraints in composer.json
composer update

# Update specific package
composer update laravel/framework

# Vulnerability check
composer audit

Python/pip: update

pip list --outdated
pip install --upgrade package-name
pip-audit  # CVE check

Dependabot: automation

# .github/dependabot.yml
version: 2
updates:
  - package-ecosystem: npm
    directory: /
    schedule:
      interval: weekly
      day: monday
    groups:
      production-dependencies:
        dependency-type: production
        update-types: [minor, patch]
    open-pull-requests-limit: 5

  - package-ecosystem: composer
    directory: /
    schedule:
      interval: weekly
    open-pull-requests-limit: 3

Testing after update

# Full check cycle
npm run build       # any build errors
npm run lint        # new warnings
npm run test        # all tests green
npm run test:e2e    # key user scenarios

Major versions: required changes examples

React 17 → 18:

  • ReactDOM.rendercreateRoot
  • Changes in useEffect with Concurrent Mode
  • Strict Mode now mounts components twice in dev

Next.js 13 → 14:

  • Pages Router → App Router (if migrating)
  • getServerSidePropsasync Server Components
  • New metadata conventions

Node.js 18 → 20:

  • crypto API changes
  • New built-in fetch (may conflict with node-fetch)

Update schedule

Type Frequency Process
Security patches Immediately (on CVE) Hotfix deploy
Patch versions Weekly Dependabot PR + auto-merge
Minor versions Monthly PR + review + testing
Major versions As needed Separate task, full testing

Monthly maintenance of average project dependencies — 4–8 hours.