ng-devtools | Devtools for angularjs | Development Tools library

A good bit of time has passed since I originally posted this question. I'll answer it myself in case my mistake can assist anyone.

I never got a "solution" to the original problem. At a much later date I switched across to the npm release of the sdk and it worked.

But before that time I'd hit this issue again. Luckily, by then, I'd added a logger that also wrote console to file. With it I noticed that a JavaScript syntax error caused the crash. e.g. Missing closing bracket, etc.

I suspect that's what caused my original problem. But the Chrome dev tools do the worst thing by blanking the console rather than preserve it when the tools crash.

Code I used to setup a logger

Since they are generated classes you have to exclude them from Spring Devtools "restart" classloader.

1. Create a /src/main/resources/META-INF/spring-devtools.properties file

2. Add properties like restart.exclude.* to exclude classes from restart classloader (example, you can use restart.exclude.mygeneratedclasses=/*[generated]*.class to exclude all classes with generated word as part of package or class name)

3. Done. Now you can use devtools and have no issues with WS generated classes.

Reference:

[1] https://github.com/spring-projects/spring-boot/issues/4529

[2] https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-devtools.html#using-boot-devtools-customizing-classload

It may be that whatever you are using to compile the changes you have made is deleting the class file and then recompiling the source rather than writing the new class file over the top of the old one. If the time between the class file being deleted and the source being recompiled is greater than DevTools' quiet period, the app will be restarted without the changed class – DevTools will believe that you have deleted it rather than changing it.

You may want to increase the quiet period so that DevTools sees both the deletion and the creation of the recompiled class file in the same batch. The default quiet period is 400ms. The following example will set it to 1 second:

@some-programmer-dude was correct. My sqlite3 install was of a 32 bit version. I just downloaded the source, built it, make, and install. Now I no longer have a missing _sqlite3 library. I made the mistake of using the precompiled linux binaries from the download page, as they only precompiled a 32 bit version. I should have just built it from the start. Thanks some-programmer-dude.

The issue is that to use non-Sweave vignettes, you have to have a vignette engine. As section 1.4.2 of the Writing R Extensions manual explains

Vignettes in formats other than Sweave are supported via “vignette engines”....

R recognizes non-Sweave vignettes using filename extensions specified by the engine. For example, the knitr package supports the extension .Rmd (standing for “R markdown”). The user indicates the vignette engine within the vignette source using a \VignetteEngine line, for example

%\VignetteEngine{knitr::knitr}

This specifies the name of a package and an engine to use in place of Sweave in processing the vignette. As Sweave is the only engine supplied with the R distribution, the package providing any other engine must be specified in the ‘VignetteBuilder’ field of the package DESCRIPTION file, and also specified in the ‘Suggests’, ‘Imports’ or ‘Depends’ field (since its namespace must be available to build or check your package).

...

Package writers who would like to supply vignette engines need to register those engines in the package .onLoad function. For example, that function could make the call

tools::vignetteEngine("knitr", weave = vweave, tangle = vtangle, pattern = "[.]Rmd$", package = "knitr")

Unfortunately, none of knitr's vignette engines (found here) use a pattern that will pickup pure md documents.

R.rsp provides a markdown vignette engine (see here and here):