Describe the bug
parse-spectra fails to process every spectrum it loads. The failure happens regardless of which flags are passed even a bare call with just -u and it fails silently, since errors during this step currently are not surfaced anywhere in the command's output.
To Reproduce
Run nmr-cli parse-spectra -u https://cheminfo.github.io/bruker-data-test/data/zipped/aspirin-1h.zip
Inspect the logs array in the JSON output
See an error entry: "Failed to parse spectrum: ... (0, nmr_processing_1.mapPeaks) is not a function"
Expected behavior
The spectrum should parse successfully with no error logged, matching normal parse-spectra behavior.
Screenshots
Node: nmr-cli's nmr-processing dependency resolves to 22.23.0
Relevant packages: @zakodium/nmrium-core-plugins requires nmr-processing: ^22.13.0, but 22.23.0 (which satisfies that range) no longer exports mapPeaks, which initiateDatum1D/ initiateDatum2D` call unconditionally on every spectrum
Additional context
Root cause is a dependency version mismatch, not something specific to this one test file. Reproduces with a completely unmodified install (verified with a fresh clean-room npm install + rebuild).
Describe the bug
parse-spectrafails to process every spectrum it loads. The failure happens regardless of which flags are passed even a bare call with just-uand it fails silently, since errors during this step currently are not surfaced anywhere in the command's output.To Reproduce
Run
nmr-cli parse-spectra -u https://cheminfo.github.io/bruker-data-test/data/zipped/aspirin-1h.zipInspect the
logsarray in the JSON outputSee an error entry:
"Failed to parse spectrum: ... (0, nmr_processing_1.mapPeaks) is not a function"Expected behavior
The spectrum should parse successfully with no error logged, matching normal parse-spectra behavior.
Screenshots
Node: nmr-cli's
nmr-processingdependency resolves to22.23.0Relevant packages:
@zakodium/nmrium-core-pluginsrequiresnmr-processing: ^22.13.0, but22.23.0(which satisfies that range) no longer exportsmapPeaks, whichinitiateDatum1D/initiateDatum2D` call unconditionally on every spectrumAdditional context
Root cause is a dependency version mismatch, not something specific to this one test file. Reproduces with a completely unmodified install (verified with a fresh clean-room npm install + rebuild).