feat: introduce devMode to support nodejs based unit testing

[zewa666]

as the title suggests this is meant to make unit/integration tests, e.g with testing-library, possible for apps using Slickgrid. In my specific case I'm making use of angular-slickgrid and would like to be able to test my app using angular-testing-library.

The introduced devMode workarounds are in order to work around the following jsdom issues:

• clientWidth returns 0 jsdom/jsdom#2310 (missing clientWidth)
• CSSStyleSheet does not have ownerNode or href properties. jsdom/jsdom#992 (missing ownerNode, even with a nice reference to Slickgrid ;) )

For additional conversations about this topic please refer to ghiscoding/Angular-Slickgrid#1319

P.S.: if this PR is fine I can later create an additional one targeting the master branch

[zewa666]

instead of the containerClientWidth property on devMode, we could as well leverage the already existing options.options.viewportMinWidthPx. The only downside is that I'm not sure whether this would introduce potential issues with the autosizeColumns feature. (see function internalAutosizeColumns(autosizeMode, isInit)).

Moreover I'm pretty sure more jsdom issues will surface as I continue testing so having devMode as a collection of "workarounds" instead of a simple boolean flag is more forward-looking

[ghiscoding]

@zewa666 so just to be clear, the devMode can be of type boolean or { ownerNodeIndex?: number; containerClientWidth?: number; }, is that correct? I'm asking because I'll have to backport this to the SlickGrid v5 with TypeScript and also into the next major major Slickgrid-Universal code

[zewa666]

exactly right. I can also do the backport to v5(master?!) as mentioned above.

[ghiscoding]

alright I'm ok with the PR then as mentioned in paragraph below. So let me go ahead and merge the PR, I'll let you do the backport to v5, thanks for that.

I'll push new SlickGrid versions and other upstream libs probably in the weekend.
On all my upstream libs, I've now switched to GitHub Action workflows to publish releases because I wanted to publish on npm with --provenance and it's now much quicker to push releases, just hit start workflow :)

[zewa666]

sounds great. getting late over here so I'll open the PR for v5 tomorrow. thx

[ghiscoding]

The Dev Mode seems like an acceptable approach for testing libraries, I think however that SlickGrid might also be used in a Node project (without a browser or maybe with Python, I don't really know) so the Dev Mode wouldn't be representative for that use case but that could be corrected in the future with another condition to the if I guess. But, I personally only ever use SlickGrid in a browser and I'm not sure how that could be used in a plain Node project (which uses global instead of window) and I guess that since we also have a few more window object usage across the project, there would be a bunch more errors to fix anyway... all that to say that I guess I'm ok with the Dev Mode approach since it doesn't introduce any breaking change and it does helps with testing libraries like Jest and and others

For anyone's reference, this PR came from a long Discussion in Angular-Slickgrid project and that project still uses SlickGrid v4 hence why this PR is based on the version4 branch