Skip to content
This repository was archived by the owner on Jun 11, 2022. It is now read-only.
This repository was archived by the owner on Jun 11, 2022. It is now read-only.

Heroku rejects builds because of fsevents #187

Open
@juanlanus

Description

@juanlanus

I ran a deploy to Heroku from my Ubuntu 20 PC.
It consistently failed reporting
npm ERR! fsevents not accessible from jest-haste-map
while loading the dependencies.
As I browsed StackOverflow, I saw a number of questions that mentioned fsevents in the pasted build logs, that's why I'm writing this here. It's a MacOs-only module.
The solution was to make fsevents optional with
npm i fsevents@latest -f --save-optional
I don't think this can be solved by this buildpack (can it?) but at least this issue and its solution could be mentioned in the troubleshooting section to save rookies like me a lot of blood and tears.

Apart from that, the buildpack worked fine. I could publish a client-only React app without having to learn about deploying, thanks you guys!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy