v0.1.15

What's Changed

• Bump minimist from 1.2.5 to 1.2.8 by @dependabot in #92
• Bump qs from 6.9.6 to 6.11.0 by @dependabot in #88
• Bump decode-uri-component from 0.2.0 to 0.2.2 by @dependabot in #89
• Bump json5 from 1.0.1 to 1.0.2 by @dependabot in #91
• Bump json5 and tsconfig-paths by @dependabot in #90
• Bump parse-url and documentation by @dependabot in #96
• Bump parse-path and documentation by @dependabot in #93
• Bump ajv and ajv-cli by @dependabot in #95

Full Changelog: v0.1.13...v0.1.15

v0.0.14 was published to NPM but doesn't have a release here as there were a few other vulnerabilities to fix that were missed by accident in v0.1.14. Hence, the skip from 0.1.13 to 0.1.15

v0.1.13

Bunch of bumps for dependencies & changed how fs module is used or not used in order to get it to work without errors in REACT project development servers where it can seem like a node script apparently.

v0.1.12

Some small changes but biggest is DC's updated in pull request 71 #71 that reorganized how sections were read to deal with duplicated data in some USGS wells.

v0.1.11

Most updates were to README.md or Documentation.

Minor updates to the dist/index.js file with most wellio code. Most changes here related to documentation.

Updated dev dependencies eslint & documentation

v0.1.10

UPDATES:

• Fixed unneeded separate wellio script for demo page and dist/index.js by using require
• Fixed bug with assumption that UWI exists in the LAS file that was causing an error with some USGS files
• Fixed another parsing bug that was preventing some USGS files from being converted.

v0.1.9

Small updates since 0.1.8 and then biggest was last pull request that adapted processing parts to handled misformed well logs from USGS around the Houston area.

v0.1.1

Changes:

• Small changes to edge cases related to syntax of LAS files that don't exactly follow standard:
• Took out fs as default file load method to avoid problems when wellio.js is used in Angular builds.
• Other small changes as described in pull requests.
• Nothing should result in breaking changes from version v0.1.0

first release

Haven't made any changes in a while but basically been at first release for a year. Code still has performance issues when las files that are inappropriately formatted. These are documented in issue #5. Should be considered therefore alpha code, but works well otherwise.