Make sure to also run build:test in the build step

[marcoroth]

This pull request makes sure that the build:test command is also run as part of the build and release step.

This way developers (especially plugin developers) can import all Stimulus' classes and types even if they are not publicly exported. We are not guaranteeing that those exports are non-breaking, but at least this will allow developers to make use of those classes even if we are not explicitly exporting them.

Importing classes would look something like:

import { Controller } from "@hotwired/stimulus"
import { TargetSet } from "@hotwired/stimulus/dist/core/target_set"
import { Context } from "@hotwired/stimulus/dist/core/context"

And types could be imported like:

import type { TargetSet } from "@hotwired/stimulus/dist/types/core/target_set"
import type { Context } from "@hotwired/stimulus/dist/types/core/context"

Resolves #623 and #638

[DEfusion]

@marcoroth has this changed since this PR? With 3.2.2 only the types are included in the files directive of the package.

Sorry for the noise, I thought I could get away with just using the types but no I need the classes in a couple of places.

[marcoroth]

Yeah, sorry for the confusion @DEfusion, this PR and the additional files in the NPM package are going to ship with the next release.

If you need them today, please use the latest dev-build on main, thank you!