Skip to content

@parcel/watcher error when regenerate package-lock.json #1

Description

@hangoocn

I have used ththis template to create my first gen 2 app, and tried to delete package-lock.json the regenerate it using npm install on windows, it build successlly in my local, but when push to remote, amplify console rebuild will Error: No prebuild or local build of @parcel/watcher found.

I checked package_lock.json, only windows prebuild is there and missing linux ones, so just rollback to the original package-lock.json and npm install on top of it to fix it, but this is not intuitive.

Not sure if this is a bug, but it actually takes me a few hours to figure out, just post it here in case anyone else experience the same.

Btw, want to thanks Gen2 team to make such a great improvement to amplify that makes dev so much easier, it is a great idea to put front-end/backend work closer and share same node_modules, and involves cdk is a great thing that removes the black box of cli. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions