Split FEAScript into modules?

[nikoscham]

Discussed in https://github.com/orgs/FEAScript/discussions/69

^{Originally posted by nikoscham March 10, 2026}
Would a fully decomposable architecture be more appropriate for the development of FEAScript (similar to the stdlib ecosystem)? The idea would be to split the system into modular packages so users can select and combine APIs depending on their needs. Below is a rough proposal for how the modules could be structured:

---

1. FEAScript-core

• Numerical methods
• Meshing tools
• Core utilities used across the ecosystem
• Basic post-processing functionality

---

2. FEAScript-models

• Implementations of physical models (e.g. heat transfer)
• Boundary conditions
• Examples and benchmark models

---

3. FEAScript-visualization

• Mesh rendering
• Advanced post-processing (e.g. with VTK.js)

---

What do you think about this approach? Also Would a fully modular architecture make FEAScript more flexible and maintainable? Are there other modules that should exist (e.g. IO or meshing)?