Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix dependencies, tests, and clean code #35

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

KyloJorgensen
Copy link
Contributor

No description provided.

.node-version Outdated Show resolved Hide resolved
"ts-node": "^8.10.2",
"tslint": "^5.20.1",
"typescript": "^3.9.10"
"@types/aws-lambda": "8.10.24",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why dependencies are downgraded?

Are those packages not respecting semver?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typescript doesn't at the least. You were getting a build error because the versions are out of sync with each other.

If we think we need to have the newer version then we should make a v2 that uses latest packages and node

Copy link
Contributor

@medikoo medikoo May 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I simply followed semever and updated packages in version range that should not introduce breaking changes.

Majority of packages on npm follow semver, so it was pretty natural move, that normally works. It's kind of surprising it isn't here.

Therefore if you're sure that some of the bumped packages do not follow semver please fix them to a specific version, but rest should be safe with ^ versioning

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@medikoo I have packages updated where it will build with the newest.

yarn.lock Outdated Show resolved Hide resolved
@perrin4869
Copy link

Merging this would fix any project using typescript 5.1: microsoft/TypeScript#54542
The dependency on @types/lodash is breaking here

@perrin4869
Copy link

@medikoo any chance you could look into this? The dependency on @types/lodash makes typescript updates very fragile

@medikoo
Copy link
Contributor

medikoo commented Aug 29, 2023

@perrin4869 thanks for heads-up, yet I'm no longer at Serverless Inc., and I don't have maintenance rights to push anything forward. AFAIK @Danwakeem takes care of handling contributions now.

@perrin4869
Copy link

maybe @czubocha or @skierkowski can help here? would alleviate a lot of pain when typescript 5.3 is released 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants