Conversation
| "devDependencies": { | ||
| "eslint": "8.39.0", | ||
| "eslint-config-axway": "8.0.0", | ||
| "eslint-config-axway": "9.0.0", |
There was a problem hiding this comment.
I wonder if we should move away from eslint-config-axway? I wouldn't be surprised if they killed the alloy and titanium environments someday.
There was a problem hiding this comment.
Looks like the next big version does this:
https://www.github.com/appcelerator/eslint-config-axway/pull/164
Removal of the +babel, +alloy, and +titanium extensions
There was a problem hiding this comment.
I'm slowing moving all tooling code from eslint to oxlint (https://www.npmjs.com/package/oxlint). It's super fast and somewhat compatible with eslint, but I dunno about the alloy specific stuff. Maybe we don't care? Maybe Alloy users should stick with eslint and that we should fork eslint-config-axway to eslint-config-titanium?
There was a problem hiding this comment.
we could ask in Slack what people use already to see if there is already a good solution. oxlint looks nice, have to take a closer look at it at some point
2 participants
npm run lintandnpm run formatto fix some lint issues