-
-
Notifications
You must be signed in to change notification settings - Fork 48
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: Update flatpak-builder dependencies, fixes #214 #215
base: master
Are you sure you want to change the base?
Conversation
Just a question, this repo never used webpack, since there is only one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove all webpack related stuff 😓
(Side note, I am not a member of this org, but since nobody reviewed this after 5 days, I just reviewed this PR, actual maintainers might have different opinions than me, but I'll say that my suggestions are at least sound by the practices of the rest of the repo)
@@ -391,11 +391,11 @@ const run = async (config) => { | |||
return | |||
} | |||
|
|||
const artifactClient = artifact.create() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name artifactClient
fits better, just use that name (despite the docs at https://www.npmjs.com/package/@actions/artifact using artifact
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will be done.
flatpak-builder/package.json
Outdated
"js-yaml": "^4.1.0" | ||
}, | ||
"devDependencies": { | ||
"eslint": "^8.49.0", | ||
"eslint": "^9.19.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DONT update eslint, it changed the entire config format between major versions. If you run npx eslint .
after this you'll get this error:
Oops! Something went wrong! :(
ESLint: 9.19.0
ESLint couldn't find an eslint.config.(js|mjs|cjs) file.
From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:
https://eslint.org/docs/latest/use/configure/migration-guide
If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.
``
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That as wel.
I wasn't sure howto build that dist/index.js - so for the quick one i used webpack as everywhere in that file webpack was referenced (because of loaders ofc.). Will remove that. |
688fe90
to
f93378a
Compare
@Totto16 can you please build dist/index.js somehow and upload it to that branch? |
After some deep dive I think you weren't that wrong with the webpack file, the generated I think you just can use the webpack config you used, install webpack and webpack-cli globally with e.g. |
What do you think about adding webpack back to the repo, so it's documented. |
For that a real maintainer needs to explain, why it isn't present in the first place... I find that a good idea, but maybe do that in a separate PR, so that this just has the needed fixes and can be merged faster, and the discussion about this might take a while |
This fixes issue #214 by updating dependencies of flatpak-builder.
Thanks for the great action!
Kind regards,
René