Next16 build files with colons in the name
Unanswered
Kurilian Bobtail posted this in #help-forum
Kurilian BobtailOP
Hey there, just testing upgrade to 16. And works nice, almost with no change for us ... but when we are building we end up with a file with
[externals]_node:inspector_ in the name. And then Github actions (and I suspect other tools) doesn't like the file having a colon in it. Because I'm migrating an existing app, its hard to debug exactly where node:inspector is coming from, or why it gets treated as external, when other node: modules don't2 Replies
Tree Pipit
hey, having the same issue, @Kurilian Bobtail , did u ever end up going around the issue? I tried going around it by zipping it, re-mapping them in next config, all to no avail. It'll work for most of the time, but some bindings still stay, and some routes end up breaking at one point.
Kurilian BobtailOP
Hey there, no I didn't find a solution.
But we didn't find any problems in the app behaviour (yet), it has only been the github actions
So we kinda sidestepped the problem
But we didn't find any problems in the app behaviour (yet), it has only been the github actions
actions/upload-artifact that was causing problems. And we were able to tweak our pipline to avoid the need for that.So we kinda sidestepped the problem