prisma

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

What's not working?

When trying to deploy the API side using the serverless integration, builds on Windows deploy correctly, but have runtime errors.

2022-06-29 15:18:20.288	ERROR	Uncaught Exception 	{"errorType":"Runtime.ImportModuleError","errorMessage":"Error: Cannot find module '..\\..\\lib\\logger'\nRequire stack:\n- /var/task/api/dist/functions/nested/nested.js\n- /var/task/nest

• auth (in progress, @ganeshmani)
• no-prisma
• plain-js
• static
• store

Let's move the CI over to Github Actions!

What happened?

When we generate a new service resource we anciently generate a server/package-lock.json.bak file

What you expected to happen

This file don't needs to be there

How to reproduce

generate a new service resource and check the path

Amplication version

0.13.1

Environment

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Waspello is using Postgres but it isn't noted anywhere, so it is confusing for the users trying to run it. We should note it in Waspello's README and link to the docs where it is explained how to setup and run Postgres.

Problem

We could improve the readability / experience reading through the library source code if there were module level docstrings.

Suggested solution

All python modules should include a docstring explaining