aperx/factorio-scenario-ExpCluster
1
0
Fork 0
mirror of https://github.com/PHIDIAS0303/ExpCluster.git synced 2026-09-21 17:04:00 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
2048de6244c80bd3494e6913e3f28724d55ddcc5
factorio-scenario-ExpCluster/CONTRIBUTING.md
T
bbassieandClaude Fable 5.1 5487976a21 Add a Node.js CI workflow that builds and tests inside clusterio 
The packages use workspace:^ and catalog: versions, so they only
resolve inside a clusterio checkout with this repository under
external_plugins. The workflow clones clusterio master, checks this
repository out into external_plugins/ExpCluster, runs pnpm install
(which runs every prepare script), then runs the tap suites.

A last step wipes dist and runs tsc --build in each package on its own.
pnpm install builds packages in dependency order, which is why the
missing project references fixed in #473 went unnoticed. On the tree
before #473 this step fails with the same five TS2307 errors.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-09 17:56:01 +00:00

1.4 KiB
Raw Blame History

Contributing

All are welcome to make bug reports, feature requests, and pull requests for our scenario. We do not require you to have any coding knowledge to make bug reports and feature requests. If you have any questions ask us in our discord.

For developers wanting to add features please follow these guidelines:

  • All lua code is documented using ldoc.
  • Set the CLUSTERIO environment variable to your clusterio development install path, the lint needs it to resolve modules/clusterio/*.
  • Lua is checked with emmylua, configured by .emmyrc.json. Install the EmmyLua extension rather than sumnekolua / luals, and use factoriomod-debug to generate the factorio api types. Note that an inline cast must be written --[[@as T]], the spaced form is not parsed.
  • Changes should be made on your own fork and merged into main through a pull request.
  • Each pull request should be limited to one feature or a few bug fixes and link to the related issue page.
  • Pull requests are automatically linted, then built and tested against the latest clusterio master.
  • Pull requests are manually reviewed to maintain code and language quality.
  • New features should have the branch names: feature/feature-name
  • Bug fixes should have the branch names: fix/bug-name
  • Commits should have meaningful messages.
Reference in New Issue View Git Blame Copy Permalink