@theerapat-s28/ts-structural-eng-tools 3.1.0 → 3.3.0

package/CHANGELOG.md

@@ -6,6 +6,51 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 
 ## [Unreleased]
 
+## [3.3.0] — 2026-11-03
+
+**Members connect to the nodes lying on them.** Draw a girder once, from support to support, and the beams framing into it and the columns landing on it are connected without splitting it by hand. The girder stays one member in the results. Nodes that just miss a member are reported, and the new `memberConnectivity` returns both lists while the user draws, so a frontend can show what is connected. Results change only for models that had a node on a member's span that the member ignored; see Changed.
+
+### Added
+
+- **Members connect to the nodes lying on them.** A model node on a member between its ends, such as where a beam frames into a girder or a column lands mid-span, is now connected to the member. You no longer need to split the member there. The member is still one member in every result: one set of end forces, one diagram over its full length, and one envelope row. Member loads keep their positions along the whole member. Each connection is listed in the new `calculationDetails.intermediateNodes` (`{ memberId, nodeId, x }[]`, type `MemberIntermediateNode`), so a frontend can mark these points. Set `connectIntermediateNodes: false` on a member to connect it only at its ends; any value other than a boolean is rejected with error 314.
+- **Near misses are reported.** A model node that is close to a member but not on it is not connected. It is now listed in the new `calculationDetails.nearMissNodes` (`{ memberId, nodeId, x, distance }[]`, type `MemberNearMissNode`) and gets a "Member connectivity" warning naming the node, the member and the distance. Close means within 1 % of the member length and at most 100 mm (`NODE_NEAR_MEMBER_RATIO` and `NODE_NEAR_MEMBER_MAX_DISTANCE`, exported from `core`).
+- **`memberConnectivity(model)`** returns the same connected nodes and near misses without analysing (type `MemberConnectivity`). It is cheap and doesn't throw for a model that is still being edited, so a frontend can show the points while the user draws. It also reports a near miss that leaves the model unstable, when `analyze` throws 304 and returns no result.
+
+### Changed
+
+- **Results change for models with a node on a member's span that was not connected before.** Such a node used to be ignored by the member. A load or support on it then either went nowhere (an unstable structure, error 304) or acted on a separate frame. Now it acts on the member. To keep the old behaviour for a member, set `connectIntermediateNodes: false` on it. Models where every node on a member is the end of one of its pieces give the same results as before.
+
+## [3.2.0] — 2026-10-31
+
+**The analysis exports lose "Frame" from their names.** A model can be members, shells or both, so `analyzeFrame` is now `analyze`, `FrameModel` is `FeaModel`, `FrameAnalysisError` is `FeaError`, and so on, and a model of shells only, such as a mat foundation, no longer needs a `members` list. Nothing breaks: the old names still work as deprecated aliases until 4.0.0, and every result is identical to 3.1.0.
+
+### Added
+
+- **New names for the analysis exports.** "Frame" now means frame members only, as in ETABS. The exports that apply to the whole model, which may have members, shells or both, are renamed:
+
+  | Before | Now |
+  | --- | --- |
+  | `analyzeFrame`, `createFrameAnalysis`, `validateFrameModel` | `analyze`, `createAnalysis`, `validateModel` |
+  | `AnalyzeFrameOptions`, `FrameAnalysis` | `AnalyzeOptions`, `Analysis` |
+  | `FrameModel`, `FrameResult`, `FrameCaseResult`, `FrameEnvelope`, `FrameMesh`, `FrameNode`, `FrameId` | `FeaModel`, `FeaResult`, `FeaCaseResult`, `FeaEnvelope`, `FeaMesh`, `FeaNode`, `FeaId` |
+  | `FrameAnalysisError`, `FrameErrors`, `FrameModelIssue`, `FrameErrorDetails` | `FeaError`, `FeaErrors`, `FeaModelIssue`, `FeaErrorDetails` |
+
+  They are exported from the same places as the old names (the package root, `/fea`, and `/core` for the errors) and behave the same: same inputs, results, and error codes and messages.
+- **`members` is optional in `FeaModel`.** A model of shells only, such as a mat foundation, can leave it out instead of passing `members: []`.
+
+### Changed
+
+- The plain `Error` that `memberDemandEnvelope` throws for an id that is not in the result says "is not in the result" instead of "is not in the frame result".
+
+### Deprecated
+
+- The names before 3.2.0, listed under **Added**, still work: each is an alias of its new name (the same function, type, error class or object), so `instanceof FrameAnalysisError` still catches every error `analyze` throws. They are marked `@deprecated`, so editors strike them through, and will be removed in 4.0.0. To migrate, rename the imports and the types; nothing else changes.
+
+### Documentation
+
+- The FEA reference page is titled **Frame and Shell Analysis** and uses the new names throughout. Its anchors follow them too (`#analyze`, `#create-analysis`, `#validate-model`, `#fea-model`, `#fea-result` and so on), so links to the old anchors such as `#analyze-frame` open the top of the page.
+- README: a second quick start, with a slab meshed into shell elements on edge beams and columns; what changes for a front end when a model has shells (generated nodes, elements, shell forces); the model and result fields at a glance; null areas compared with shells; running in a Web Worker, with measured analysis times; and the shell error codes 326–329.
+
 ## [3.1.0] — 2026-10-31
 
 **Engine reorganised, and a guide for upgrading from 2.x.** The analysis engine behind `/fea` is reorganised into separate parts for frame members, shell elements and the analysis that runs them together. Nothing you call changes: every export keeps its name, its import path and its behaviour, and every result is identical to 3.0.0. Coming from 2.x? Read **Upgrading from 2.x** below; it covers this release and 3.0.0 together.
@@ -214,7 +259,9 @@ Maintenance release with no changes to the library code.
 
 First version, under the unscoped name `ts-structural-eng-tools`: `rectBeamMomentCapacity` (singly and doubly reinforced rectangular beams per ACI 318-19), steel plate jacketing, and concrete property helpers.
 
-[Unreleased]: https://github.com/theerapat-s28/ts-structural-eng/compare/v3.1.0...HEAD
+[Unreleased]: https://github.com/theerapat-s28/ts-structural-eng/compare/v3.3.0...HEAD
+[3.3.0]: https://github.com/theerapat-s28/ts-structural-eng/compare/v3.2.0...v3.3.0
+[3.2.0]: https://github.com/theerapat-s28/ts-structural-eng/compare/v3.1.0...v3.2.0
 [3.1.0]: https://github.com/theerapat-s28/ts-structural-eng/compare/v3.0.0...v3.1.0
 [3.0.0]: https://github.com/theerapat-s28/ts-structural-eng/compare/v2.3.0...v3.0.0
 [2.3.0]: https://github.com/theerapat-s28/ts-structural-eng/compare/v2.2.0...v2.3.0