Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign up9.0.0-rc.4 build - createWebpack(...).pipe is not a function #16316
Comments
This comment has been minimized.
This comment has been minimized.
Are you using nx within the workspace? |
This comment has been minimized.
This comment has been minimized.
yes. Sorry I forgot to mention that :S |
This comment has been minimized.
This comment has been minimized.
This might be similar to #16207 |
This comment has been minimized.
This comment has been minimized.
Hey @intellix, I think you may have You should also update |
This comment has been minimized.
This comment has been minimized.
@angular-devkit/architect wasn't in our package.json but we updated @nrwl to latest and it got us a step further. Now it's just:
When doing:
If we build without the Tried to inspect and break on errors. Got errors like the "object could not be cloned" with a reference to a part of our angular.json file: The app config looks like:
Not sure if it's related to the build error but. Updating to rc.5 changed nothing either |
This comment has been minimized.
This comment has been minimized.
Did you get a stack trace for the error? |
This comment has been minimized.
This comment has been minimized.
nope unfortunately not. I'll try and get more information |
This comment has been minimized.
This comment has been minimized.
@intellix Have you tried with the latest |
This comment has been minimized.
This comment has been minimized.
Not quite sure how to get more information really. If I do an --inspect-brk the debug server just dies at the very end. If I try to break on exceptions I'm getting a billion module resolver errors which could take years to step through! If I do an
Currently:
nrwl deps:
Resolutions:
|
Command (mark with an
x
)Description
A clear and concise description of the problem...ng build --prod gives a
createWebpack(...).pipe
error when trying to build after:ng update @angular/cli @angular/core --force
. Serving the project works perfectly fine.ng build --prod
I'm not sure if you have enough to debug here. Didn't find any related issue so am creating this with all the info I have. I can debug further with some guidance.