feat: update node image #90
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aldbr
force-pushed
the
main_FEAT_update-node-image
branch
from
4112046 to
171c54f
Compare
aldbr
force-pushed
the
main_FEAT_update-node-image
branch
2 times, most recently
from
c5d6e5a to
decacb0
Compare
aldbr
force-pushed
the
main_FEAT_update-node-image
branch
from
decacb0 to
0ce806a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#77 is stuck and I need to update the node image to keep working with a mounted
diracx-webversion as NextJS14 does not supportnode v16anymore (deprecated by the way).Update: I found a minor issue where the
diracx-webpod does not start ifnode_modulesor.nextdirectories do not exist. I fixed that by:mkdir -pline inrun_demo. It solves the issue and works correctly, now I am not sure whether it is elegant.next-env.d.tsis generated/updated bynpm run dev. As we are in development mode, it would not a problem, wouldn't it? + There is an attempt to move this file into the.nextdirectory, let's see how it goes.