Summary

Update dependencies, build, and testing for Spina.

Review Request #14638 — Created Oct. 16, 2025 and submitted Dec. 5, 2025, 11:21 a.m.

Information

Owner

david

Repository

Spina

Branch

master

Bugs

Depends On

Reviewers

Groups

beanbag-misc

People

Description

This change accomplishes several tasks towards unifying our JavaScript
build infrastructure:

Replace many specific dependencies with new dependencies on our
metapackages (@beanbag/js-buildkit and
@beanbag/frontend-buildkit).
Update package.json scripts to be more consistent with our other
packages (build, clean, full-build, lint, and test).
Use @babel/register for transpiling during jasmine testing rather
than ts-node. It seems like the ts-node one was broken on modern
jasmine and/or node as it was, and using babel instead keeps our
unit tests running in a much closer mode to how the code is built
for packaging anyway.
Base tsconfig.json on our shared config.
Update for eslint 9.

Testing Done


Did builds and installed both in isolation as well as in a workspace

  with a bunch of our other JS packages.
Ran unit tests.
Ran eslint (there are a bunch of existing errors that it's showing).
Ran npm pack and verified that the resulting tarball included all

  the expected files.

Commits

Summary	ID
Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing). - Ran `npm pack` and verified that the resulting tarball included all the expected files.	pqykrxpuxotrkksutylxoxuxrsvnuwnx

Summary

Update dependencies, build, and testing for Spina.

This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing). - Ran `npm pack` and verified that the resulting tarball included all the expected files.

pqykrxpuxotrkksutylxoxuxrsvnuwnx

Issues

Description	From	Last Updated
Can you generate a source dist with this and a source dist before this and diff them, make sure no …	chipx86	Nov. 3, 2025, 8:56 a.m.
Can you add module docs with a Version Added to this file?	chipx86	Nov. 3, 2025, 8:52 a.m.

flake8 passed.

JSHint passed.

Change Summary:


Improve babel config to share everything for dev and test.
Export types as both .d.ts and .d.mts.
Fix jasmine helper paths.

Commits:

	Summary	ID
	Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing).	pqykrxpuxotrkksutylxoxuxrsvnuwnx
	Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing).	pqykrxpuxotrkksutylxoxuxrsvnuwnx

Diff:

Revision 2 (+6414 -4824)

Show changes

	.eslintrc.yaml
	babel.config.json
	eslint.config.mjs
	package.json
	package-lock.json
	rollup.config.js
	tsconfig.json
	spec/helpers/babel.js
	1 more

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Change Summary:


Update eslint config for newer plugin.
Add jquery as an optional peer dependency.
Exclude package-lock.json from the posted diff for easier reviewability.

Commits:

	Summary	ID
	Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing).	pqykrxpuxotrkksutylxoxuxrsvnuwnx
	Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing).	pqykrxpuxotrkksutylxoxuxrsvnuwnx

Diff:

Revision 3 (+226 -216)

Show changes

	.eslintrc.yaml
	babel.config.json
	eslint.config.mjs
	package.json
	rollup.config.js
	tsconfig.json
	spec/helpers/babel.js
	spec/support/jasmine.json

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

The issue has been resolved. Show all issues

Can you generate a source dist with this and a source dist before this and diff them, make sure no files are missing and the results look as expected?

eslint.config.mjs (Diff revision 3)
The issue has been resolved. Show all issues
```
Can you add module docs with a Version Added to this file?
```

Testing Done:

		Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages.
		Ran unit tests.
		Ran eslint (there are a bunch of existing errors that it's showing).
	+	Ran `npm pack` and verified that the resulting tarball included all the expected files.

Commits:

	Summary	ID
	Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing).	pqykrxpuxotrkksutylxoxuxrsvnuwnx
	Update dependencies, build, and testing for Spina. This change accomplishes several tasks towards unifying our JavaScript build infrastructure: * Replace many specific dependencies with new dependencies on our metapackages (`@beanbag/js-buildkit` and `@beanbag/frontend-buildkit`). * Update package.json scripts to be more consistent with our other packages (`build`, `clean`, `full-build`, `lint`, and `test`). * Use `@babel/register` for transpiling during jasmine testing rather than `ts-node`. It seems like the `ts-node` one was broken on modern jasmine and/or node as it was, and using babel instead keeps our unit tests running in a much closer mode to how the code is built for packaging anyway. * Base tsconfig.json on our shared config. * Update for eslint 9. Testing Done: - Did builds and installed both in isolation as well as in a workspace with a bunch of our other JS packages. - Ran unit tests. - Ran eslint (there are a bunch of existing errors that it's showing). - Ran `npm pack` and verified that the resulting tarball included all the expected files.	pqykrxpuxotrkksutylxoxuxrsvnuwnx

Diff:

Revision 4 (+242 -218)

Show changes

	.eslintrc.yaml
	babel.config.json
	beanbag-spina-3.1.2.tgz
	eslint.config.mjs
	package.json
	rollup.config.js
	tsconfig.json
	spec/helpers/babel.js
	1 more

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to master (f2a4f4e)

eslint.config.mjs (Diff revision 3)