Skip to content

Fixed version in package.json for local environment #25

@deemount

Description

@deemount

I have tried a few ways to create an app locally and then deploy it via a Github repository. One variant that gives me a headache, for example, is Vite+Vanilla JS. I have therefore decided to use this template in order to make progress. But here, too, I encountered problems.

Description

  1. I ran git clone of the deployed app and switched to the local workspace of the repository (VSCode). I ran npm install to download the dependent modules. The download was canceled because “esbuild”: “^0.20.2” in the package.json was outdated. After I changed the value to the recommended version “esbuild”: “^0.23.1”, the modules could be downloaded (not without warnings, as they were also outdated/ deprecated).

  2. I tried to run the app locally with npm run dev, but failed, because the amplify_output.json is missed. I've got my amplify_outputs.json with the the command npx ampx sandbox and after three minutes of building so, I could see the website under 127.0.0.1:5173

  3. Finally, of course, I have to add that I read the documentation AWS Amplify on this a little later ;)

Conclusion

I know that the package.json must also be adapted by developers themselves from time to time if they want to use certain packages. With AWS Amplify, however, some things do not seem to have been clarified yet. Especially, when it comes to the many different versions.

That's why I would like to help to identify the small errors here to guarantee a smooth creation and deployment process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions