Ensure the matching version of the assets package is installed

[thatbudakguy]

Because the "latest" npm package version is not related to the newest semver version, doing a yarn add blacklight-frontend with no version specifier currently results in retrieving v7.38.0, even though versions for v8.x are published.

This means a new Blacklight 8 app with propshaft will not retrieve the correct asset package.

This ensures that we get the npm asset version that matches Blacklight's version by asking for it explicitly, even if it has not been marked latest. If there is a mismatch between npm package versions and Blacklight gem versions, we'll get an error.

[jrochkind]

Are you going to run this generator past initial app generation?

I think I've seen other things do a run-time check on startup by shelling out to yarn to make sure that that npm installation matches the rubygems installation. I think ruby-vite might do that for instance.

I wonder if that would be better than pinning on generation -- with a pin that needs to be updated manually on every upgrade. The pin on generation only produces a different result than before if you are installing a non-latest BL.

[thatbudakguy]

with a pin that needs to be updated manually on every upgrade

Isn't this what you want? I think you don't want the frontend asset package version changing under you unless you also change the gem version, right?

[jrochkind]

Yes, I guess that makes sense! I was thinking of the case where you forget to update the package.json pin, which I think people will frequently forget to do, and get no warning of it. But perhaps this solves a different problem!