AnimalRequests: package updates

[labkey-nicka]

Rationale

Client-side package updates for the AnimalRequests module.

Related Pull Requests

• AnimalRequests: package updates #977
• Virology: package updates #978
• Purchasing: package updates #979
• WNPRC_EHR: package updates #980
• CageUI: package updates #981

Changes

• Package updates
• Migrate app to use @labkey/build
• app and dev views automatically generated by @labkey/build
• Revise scripts in package.json to match present day configuration
• Remove unused betterScripts

[aschmidt34]

I have 2 questions before I approve:

1. I noticed package.json change version 1.1.0 to 0.0.0. Shouldn't 0.0.0 only be used in a non-production environment? Is this okay?
2. I noticed our 'reallyClean' command was removed; however, we still use that. Was that an accident?

[labkey-nicka]

1. I noticed package.json change version 1.1.0 to 0.0.0. Shouldn't 0.0.0 only be used in a non-production environment? Is this okay?

This isn't a package that is published with a version to a npm package repository. This is used solely for building client-side applications within this LabKey module. We can leave it as 1.1.0 but the version does not serve a purpose and has no meaning in the context of a LabKey module.

2. I noticed our 'reallyClean' command was removed; however, we still use that. Was that an accident?

I removed it since there was not a correlated better-npm-run command for reallyClean so it seems to be at best a no-op. Perhaps this is a built-in mechanism of better-npm-run that I was not aware of.