2021-05-11
2925
#node#react
Geshan Manandhar
47599
May 11, 2021 ⋅ 10 min read

Deploying a full-stack Node.js + React app for free with Begin

Geshan Manandhar Geshan is a seasoned software engineer with more than a decade of software engineering experience. He has a keen interest in REST architecture, microservices, and cloud computing. He also blogs at geshan.com.np.

Recent posts:

Debugging with Chrome DevTools MCP: Giving AI eyes in the browser

Debugging with Chrome DevTools MCP: Giving AI eyes in the browser

Learn how to effectively debug with Chrome DevTools MCP server, which provides AI agents access to Chrome DevTools directly inside your favorite code editor.

Emmanuel John
Oct 21, 2025 ⋅ 6 min read
Goodbye, useState? Smarter state modeling for modern React apps

Goodbye, useState? Smarter state modeling for modern React apps

Ever opened a React file and found a graveyard of useState hooks? The problem isn’t React; it’s how we model state. Here’s how to do it smarter.

Oscar Jite-Orimiono
Oct 21, 2025 ⋅ 9 min read

Why third-party integrations break in React 19 — And how to future-proof them

React 19 breaks old third-party integrations. Learn why concurrent rendering exposes brittle SDKs and how to rebuild them with resilient modern patterns.

Peter Aideloje
Oct 20, 2025 ⋅ 4 min read
React useEffectEvent: Goodbye to stale closure headaches

React useEffectEvent: Goodbye to stale closure headaches

Discover why the useEffectEvent Hook is important, how to use it effectively, and how it compares to useRef.

David Omotayo
Oct 17, 2025 ⋅ 5 min read
View all posts

2 Replies to "Deploying a full-stack Node.js + React app for free with Begin"

  1. Hi Geshan Manandhar,

    I followed steps mention in this guide, but test are failing. Can you help me resolving this issue. Test are passing on local machine but failing on begin site.

    > [email protected] test /tmp/cf9dd36c4da4-4fb2-b199-0f30d828c05f
    > cross-env NODE_ENV=testing PORT=6666 tape test/**/*-test.js test/*-test.js | tap-spec

    Set up env

    ✔ sandbox loaded

    Start the Sandbox

    App ⌁ react-hello
    Region ⌁ us-west-2
    Profile ⌁ @aws profile / AWS_PROFILE not configured
    Version ⌁ –
    cwd ⌁ /tmp/cf9dd36c4da4-4fb2-b199-0f30d828c05f
    ✓ Sandbox Found Architect project manifest: package.json
    ✓ Sandbox No testing environment variables found
    ✓ Sandbox Project files hydrated into functions
    ✓ Sandbox Started service discovery emulator
    ✓ Sandbox Loaded routes (HTTP API mode / Lambda proxy v2.0 format)
    get /api ………………………… api
    http://localhost:6666

    ✓ Sandbox Started in 26ms
    ❤︎ Local environment ready!
    ✔ should be strictly equal

    get /api

    events.js:291
    throw er; // Unhandled ‘error’ event
    ^

    Error: spawn ps ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
    at onErrorNT (internal/child_process.js:470:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
    Emitted ‘error’ event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
    at onErrorNT (internal/child_process.js:470:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
    errno: ‘ENOENT’,
    code: ‘ENOENT’,
    syscall: ‘spawn ps’,
    path: ‘ps’,
    spawnargs: [ ‘-o’, ‘pid’, ‘–no-headers’, ‘–ppid’, 153 ]
    }
    npm ERR! Test failed. See above for more details.

Leave a Reply

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now