Consider replacing node-libofx package with ofx-js #91

Closed
opened 2026-02-28 18:48:19 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @TomAFrench on GitHub (May 18, 2022).

Something that stands out to me is that we're using in a parser written in C++ to read OFX/QFX files. This is the downside that we need to then compile this to wasm and have glue code to interact with this.

Considering we're just using this for importing the OFX/QFX files, is there any reason that we can't use a native javascript parser such as https://github.com/bradenmacdonald/ofx-js?

This seems quite tempting to me as we could knock out one of our packages entirely but there may be other reasons why it is as it is.

Originally created by @TomAFrench on GitHub (May 18, 2022). Something that stands out to me is that we're using in a parser written in C++ to read OFX/QFX files. This is the downside that we need to then compile this to wasm and have glue code to interact with this. Considering we're just using this for importing the OFX/QFX files, is there any reason that we can't use a native javascript parser such as https://github.com/bradenmacdonald/ofx-js? This seems quite tempting to me as we could knock out one of our packages entirely but there may be other reasons why it is as it is.
Author
Owner

@TomAFrench commented on GitHub (Aug 20, 2022):

Closing this based on feedback from James in the PR

@TomAFrench commented on GitHub (Aug 20, 2022): Closing this based on feedback from James in the PR
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#91