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:

react toastify

React-Toastify (2025 update): Setup, styling & real-world use cases

Learn how to use React-Toastify in 2025, from setup to styling and advanced use cases like API notifications, async toasts, and React-Toastify 11 updates.

Chimezie Innocent
Apr 18, 2025 ⋅ 18 min read
5 Best Open Source Tools For Cross-Browser CSS Testing

5 best open source tools for cross-browser CSS testing

Discover open source tools for cross-browser CSS testing like Playwright and BrowserStack to catch rendering errors, inconsistent styling, and more.

Peter Aideloje
Apr 18, 2025 ⋅ 11 min read
react suspense data fetching

How to handle data fetching with React Suspense

With the introduction of React Suspense, handling asynchronous operations like data fetching has become more efficient and declarative.

Ovie Okeh
Apr 18, 2025 ⋅ 10 min read
Use TypeScript Instead Of Python For ETL Pipelines

Use TypeScript instead of Python for ETL pipelines

Build a TypeScript ETL pipeline that extracts, transforms, and loads data using Prisma, node-cron, and modern async/await practices.

Muhammed Ali
Apr 17, 2025 ⋅ 6 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