Skip to content

refactor: switch to single config file and deno.json again #103

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

csvn
Copy link
Contributor

@csvn csvn commented May 16, 2025

Given what's mentioned by @crowlKats in #101 (comment), I thought perhaps it's better to combine deno.json + package.json into only deno.json once more. Given that all metadata for the action comes from action.yml.

The version field in deno.json can instead be used if it's preferable to have PR's (e.g. #102) when new versions are released. The only field that has no equivalent in deno.json is the author field, though I don't think there's any purpose to it when this field exists in action.yml.

@csvn csvn requested a review from lucacasonato as a code owner May 16, 2025 14:25
Comment on lines +2 to +6
"name": "@deno/setup-deno",
"description": "Set up Deno easily in GitHub Actions",
"version": "2.0.3",
"license": "MIT",
"exports": "./src/cache.ts",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The exports property was needed since I added the name property with @deno/setup-deno to mimic package.json. Though both can be removed preferable.

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.

1 participant