When working on in-progress Capital Framework components, it's difficult to sym-link every component. We already have a NPM link script in the Capital Framework project, this does the other half of NPM linking.
Additions
NPM linking and unlinking scripts
Testing
In your main CF repo, run npm run cf-link to create the locally available packages
In this repo, run npm run cf-link to create the second half of the links.
In this repo, run grunt less && npm start You should now be able to make changes to the CF source code, and see them in this project. Note that you'll probably need to kick off the appropriate build task in the secondary repo, as Grunt doesn't watch the node_modules directory for changes, typically it's grunt less
To reset this repo, run npm run cf-unlink. This will remove the sym-link and reinstall the latest version of each component that matches in package.json.
While not typically necessary, this would make it a lot easier to update the Design Manual for breaking changes in the future, vs updating it far after a major release of Capital Framework.
Checklist
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
Scotchester
commented
7 years ago
When working on in-progress Capital Framework components, it's difficult to sym-link every component. We already have a NPM link script in the Capital Framework project, this does the other half of NPM linking.
Additions
Testing
npm run cf-linkto create the locally available packagesnpm run cf-linkto create the second half of the links.grunt less && npm startYou should now be able to make changes to the CF source code, and see them in this project. Note that you'll probably need to kick off the appropriate build task in the secondary repo, as Grunt doesn't watch thenode_modulesdirectory for changes, typically it'sgrunt lessTo reset this repo, runnpm run cf-unlink. This will remove the sym-link and reinstall the latest version of each component that matches inpackage.json.Review
Preview this PR without the whitespace changes
Notes
While not typically necessary, this would make it a lot easier to update the Design Manual for breaking changes in the future, vs updating it far after a major release of Capital Framework.
Checklist