You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Documentation issue or request
The problem
After rebasing and using the latest changes with Angular 6.0.4 I started to get the following error coming from the yamljs package when I'd try to rebuild with yarn ng build --aot=false --vendor-chunk=true --source-map=true or even just syndesis build --clean, which uses the same command.
Screenshot
ERROR in ./node_modules/yamljs/lib/Utils.js
Module not found: Error: Can't resolve 'fs' in '/Users/kahboom/Projects/syndesis/app/ui/node_modules/yamljs/lib'
Well, if this is the same issue I'm thinking of, I was trying to come up with a fix that would work for everyone without having to use the --force flag. I think this is related to the version of Node and npm each person uses and dependencies that try to force certain engine versions. Either way, this commit would have sorted out for local env, but not for CD/CI: https://github.com/syndesisio/syndesis/pull/2886/files#diff-4c51b5da64219cce10752e61a6393f5c
I guess either way we can consider this closed and just have people run those commands manually, or that fix above should sort it out.
This is a...
The problem
After rebasing and using the latest changes with Angular 6.0.4 I started to get the following error coming from the yamljs package when I'd try to rebuild with
yarn ng build --aot=false --vendor-chunk=true --source-map=true
or even justsyndesis build --clean
, which uses the same command.Screenshot
See my comment here for more details.
I also got a few other weird things related to SASS:
EDIT: This should be resolved with this PR #2886 .
The text was updated successfully, but these errors were encountered: