Update README.md with running FEC locally instructions #2139
Conversation
|
|
||
| This set up should work with most applications but individual apps may have dependency conflicts. | ||
| In this example Insights-Inventory-Frontend will be used | ||
| - In FEC, navigate to packages/components -> here run `npm link` |
There was a problem hiding this comment.
Should this not be done within the dist folder?
There was a problem hiding this comment.
I hadnt done so, I followed those instructions exactly and was able to get it to work with three different repos
There was a problem hiding this comment.
@adonispuente Please doublecheck that you do not have any leftover assets within the packages/components folder for example. Within these folders there should only be folders like src/lib or docs, If you see ".js" files they are probably old and outdated. This could be why it still works for you, because not linking it from within the dist folder doesn't work for me. ;)
| - In FEC, navigate to packages/components -> here run `npm link` | ||
| - In Inventory root, run `npm link @redhat-cloud-services/frontend-components` | ||
| - Verify it actually linked with `ls -l node_modules/@redhat-cloud-services/frontend-components` | ||
| - In Inventorys fec.config.js , attach |
There was a problem hiding this comment.
@Hyperkid123 Maybe we could add this to the fec CLIs config and enable it automagically when it sees any symlink in the @redhat-cloud-services packages?
No description provided.