Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

React 18.3.1, bootstrap 5.3.3, @rjsf/core 5.23.1 #1847

Draft
wants to merge 28 commits into
base: master
Choose a base branch
from

Conversation

naugehyde
Copy link

Updated with React 18.3.1, bootstrap 5.3.3 and @rjsf/core 5.23.1 support.

Issues

  1. multiple stylesheet issues
  2. server-admin-ui/logging throws runtime error:
bootstrap.js:240 Uncaught ReferenceError: Cannot access 'html' before initialization
    at bootstrap.js:240:12
    at dispatch (redux.mjs:160:1)
    at redux-thunk.mjs:7:1
    at ws.onmessage (actions.js:170:7)

  1. server-admin-ui update untested

tkurki and others added 26 commits November 27, 2024 21:54
For some reason we had both rmfr and rimraf. Use just
rimraf's latest version.
Don't run tests with 16 any more. For example structuredClone
is needed by dev tooling.
serialport module has been optional, as it is platform specific and
its install may fail but otherwise the server would be in working order.

However when converting serialports.js to ts using import had made
it a hard dependency - the server would not start without it,
even if npm install had completed without errors but without
serialport still installed.

Use dynamic require to load it so that even if the module
is missing the server starts.
…xtPoint.position value when stream source is the cmdSource. (SignalK#1844)
@tkurki
Copy link
Member

tkurki commented Dec 15, 2024

For me to be able to review this I need to be able to distinguish between changes that have already been merged, like the ts related updates, and what are the actual changes in this PR. The best way to achieve that would be to rebase this branch on master. Is this something you can do? I can assist if needed.

@naugehyde
Copy link
Author

I rebased two days ago (or at least thought I did). If there are additional steps I need to take please let me know what I need to do.

@tkurki
Copy link
Member

tkurki commented Dec 15, 2024

Have you pushed your changes to this branch to your fork of the repository? The commit history now has a lot of commits that are already in master, they should not be there after successful rebase and force push.

@naugehyde
Copy link
Author

naugehyde commented Dec 15, 2024 via email

@tkurki
Copy link
Member

tkurki commented Dec 15, 2024

It is safe (as long as you overwriting the repo with correct content) and yes -f will do it.

@naugehyde
Copy link
Author

naugehyde commented Dec 15, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants