Aaron Huggins

@notfilippo and @ebebbington: Is this a good fit, or shall I go ahead and close this issue?

Hey, @notfilippo, let's do it. At least this way, with this codebase, there's a good bootstrapped way to get PouchDB working correctly *until* that project implements Deno support natively. I've...

First of all, sorry for the very late reply. X12 has ended up low priority due to some unexpected life circumstance stuff. Second, this is REALLY weird for a bug....

@pomSense Do you have an example of the dataset that's triggering the error? The parser is expecting to encounter an element delimiter to instantiate `currentElement`; if no delimiter is encountered,...

Hey, @pomSense! Your issue might be related to this PR: #26 All code from the PR should be in the beta: `npm install node-x12@beta` Please give that a try and...

@pomSense The Deno migration may have uncovered the source of the bug you are reporting. I think I need to change https://github.com/aaronhuggins/node-x12/blob/a1d2515faca8ae98c5a7d131f03fc04b43c33865/src/X12Parser.ts#L202-L205 to definitely assign `currentElement`, like: ```typescript let currentSegment:...

Hey @pomSense! Got my attention while I'm kid-free for a few minutes! > Do you still want me to give this a try or wait for port back to 1.7.x?...

Build action is running... 

Pre-released! 

@Jelenbl I can't read your report. Please reformat so I can understand quoted vs JavaScript vs output vs sample. Please also provide an attached text file with a sample 997...