ally.js | JavaScript library to help modern web applications | User Interface library

When you build in prod mode, angular tries to extract licenses from the 3rd party libs that you use into a 3rdpartylicenses.txt file. For that, it needs looking at package.json files.

Since you put your handontable package manually in your node_modules, it's missing package.json.

What you should really do is install handontable with npm (specify the version if needed)

Here is a basic python script that will do this. You can create a json file and ready from it and overwrite the new data every time.

So I found the issue was with the order that I was resolving code. It took forever to find because there was nothing inherently wrong with my code, but the sequence was wrong.

I was calling everything in the correct order, but the order that things were resolving in my network panel were incorrect.

Once I fixed the sequence that things were being loaded into the DOM, everything worked as expected.

Fix #1

Because my XMLHttpReqests should be asynchronous, I put all the calls into a single Javascript file so they would run synchronously.

I needed Javascript files to be loaded in the tag before loading function calls that reference those files.

The function calls I wrapped in window.onload = function(){}.

Basically my final solution was for any that I was dynamically placing in example.html I would wrap in window.onload = function(){}.

i.e.

Fix #2

I was using the onload wrapper window.onload = function(){} in a location that did not make sense. Also it may have been nested within another window.onload function at one point while debugging, which probably didn't help.

I solved my issue. The codeslide tag cannot be contained within the slide component as they are effectively the same thing. I've changed and working now.

I believe it has to do with inlined source maps.

Check again with a production-ready value for webpack devtool option (or none): https://webpack.js.org/configuration/devtool/

you can also try the option mode: 'production', but I don't recommend using that during development

This was caused by an error of my own in my projects/example.yaml, as well as an issue that was fixed by https://phabricator.wikimedia.org/T227842

The finally block will run after the contents of the try block, not necessarily the whole test. Things like errors and exceptions are meant to be caught in the try block but with a timeout, the error is thrown by mocha (so outside of your try block).

If you need to run the finally block after the test is finished and it is taking too long, you can change the default timeout by putting

this.timeout();

inside of your it function (or the describe function if you want it to apply to everything).

If you are wanting to do the same thing after every test, then yes the afterEach() function is the way to go.

To catch it this is enough: