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: bump GCS dependency to support Node 20 #145

Merged
merged 6 commits into from
Feb 5, 2024
Merged

fix: bump GCS dependency to support Node 20 #145

merged 6 commits into from
Feb 5, 2024

Conversation

wkillerud
Copy link
Contributor

Drop support for Node 12, 14, 16

@wkillerud wkillerud mentioned this pull request Feb 5, 2024
@wkillerud
Copy link
Contributor Author

I see a potential problem, in that this package creates an executable using vercel/pkg, which was recently deprecated/archived. It only has support for building Node 18 executables.

I assume this happens when importing parts of this package in another script @stalet, not using the CLI, since the bug is an issue in Node 20? In other words it should probably be fine.

@wkillerud
Copy link
Contributor Author

On a second scan, these built executables are only attached to the GitHub Releases. For npm/node, the binary is https://github.com/finn-no/cdn-uploader/blob/master/index.js

@stalet
Copy link
Contributor

stalet commented Feb 5, 2024

Yeah it was just invoked from a build using node 20, and it seems to use the current node when invoking it.

@wkillerud wkillerud merged commit f5a6e07 into master Feb 5, 2024
2 checks passed
@wkillerud wkillerud deleted the node20 branch February 5, 2024 12:30
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.

2 participants