-
Notifications
You must be signed in to change notification settings - Fork 12
enhance: export custom nextjs/socket.io server #33
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
Conversation
- fix production NextJS builds - normalize import formatting Signed-off-by: Nick Hale <[email protected]>
Package and export a function for creating the custom combination NextJS/socket.io server so the UI can be more easily imported by other projects. Signed-off-by: Nick Hale <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lots of nits, nothing blocking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
non-blocking for this pr, but...
What's your opinion about making this a TypeScript file? A part of the socket server being so bad is that it ignore all the other TS conventions in the app since its in common js.
The package version ranges specified in package.json cause peer dependency conflicts when package-lock.json is removed. Since npm's dependency resolution doesn't consider the versions tracked in package-lock.json, any project that depends on the UI will need to resolve these issues. To fix this, pin the versions of problematic packages to the versions currently set in package-lock.json. Signed-off-by: Nick Hale <[email protected]>
8cdad2f to
67a41e8
Compare
Since the THREADS_DIR environment variable is retrieved on package import, changes that dependents make to it before startAppServer is called are ignored. To fix this, load the environment variable immediately before it's used instead. Signed-off-by: Nick Hale <[email protected]>
7b9a4df to
9b50bdd
Compare
Uh oh!
There was an error while loading. Please reload this page.