Make ES5 compatible

[JakobMiksch]

fixes #73

This PR attempts to make geoserver-node-client compatible to ES5.

• Note: importing the library via git does not work for ES5:

"geoserver-node-client": "git+https://github.com/jakobmiksch/geoserver-node-client.git"

TODO:

• ensure it works in combination with release-it, fixed with e1910ad
• include ES5 version in CI tests --> Issue moved to Test ES5 functionality in test suite #82

[JakobMiksch]

@chrismayer this commit e1910ad should ensure that release-it also builds the ESM5 compatible code.
I tested it with the dry run functinality: npx release-it --dry-run and the produced commands looked like expected (see below). So, I am optimistic that it will work in production as well.

? Select increment (next version): patch (0.0.8)
! npm version 0.0.8 --no-git-tag-version
! npm run build                                    <-- HERE RELEASE-IT TRIGGERS THE BUILT
$ git status --short --untracked-files=no

Empty changeset

! git add . --update
? Publish geoserver-node-client to npm? Yes
$ npm publish . --tag latest --dry-run
? Commit (Release 0.0.8)? Yes
! git commit --message Release 0.0.8
? Tag (0.0.8)? Yes
! git tag --annotate --message Release 0.0.8 0.0.8
? Push? Yes
$ git symbolic-ref HEAD  [cached]
$ git for-each-ref --format="%(upstream:short)" refs/heads/esm-approach  [cached]
! git push --follow-tags
🔗 https://www.npmjs.com/package/geoserver-node-client
🏁 Done (in 27s.)

[JakobMiksch]

@chrismayer the commit 9a66c88 also exposes the GeoServerResponseError to the user of the library. This can be useful to perform error handling based on different kinds of errors. Similar to the code below. Does this make sense to you?

try {
  myroutine(); // may throw three types of exceptions
} catch (e) {
  if (e instanceof TypeError) {
    // statements to handle TypeError exceptions
  } else if (e instanceof RangeError) {
    // statements to handle RangeError exceptions
  } else if (e instanceof EvalError) {
    // statements to handle EvalError exceptions
  } else {
    // statements to handle any unspecified exceptions
    logMyErrors(e); // pass exception object to error handler
  }
}

(taken from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch#conditional_catch-blocks )

[chrismayer]

exposes the GeoServerResponseError to the user of the library. This can be useful to perform error handling based on different kinds of errors. Similar to the code below. Does this make sense to you?

Yes, makes totally sense. +1 for this. We just have to clarify where the export itself should be placed best. See my comment above.

[JakobMiksch]

@chrismayer I responded to your comment inline.

[chrismayer]

Since the Error stuff is moved to a separate PR (#83) this is good to go.