This directory is currently a mix of vendoredĭependencies, forked dependencies and Light Table specific libraries: Node dependencies are at deploy/core/node_modules/. Vendored dependencies are "dependencies" in package.json.These are dependencies that should not be modified and should be updated with upstream versions.
DOC WINDOW IN LIGHTTABLE PANE SIZEL INSTALL
To update an individual dependency: cd deploy/core & npm install e.g.Doc window in lighttable pane sizel update# Npm install To see outdated dependencies: npm outdated. Dependencies should not be updated without good QA and checking the dependency's changelog.ĭoc window in lighttable pane sizel install#.Forked dependencies are "forkedDependencies" in package.json.These packages have had custom commits that should get sent upstream.These should eventually become vendored dependencies. Some of them differ slightly from the original e.g.codemirror_addons - Provides codemirror addons.lighttable - Mostly lighttable js libs except for lighttable/util/ which should be moved to vendored dependencies.Īllows us to build cross platfrom desktop apps.
DOC WINDOW IN LIGHTTABLE PANE SIZEL CODE
See Electron guide Other Running Light Table Code in Light Table Generally, and unless you know what you're doing, do not eval entire files of the Light Table source eval individual forms.Īs Gabriel explains in this comment in issue #2170:ĭepending on the file you're re-evaling, a whole file re-eval often redefines core LT object types and recreates LT objects. This can have dire consequences in some files e.g. re-evaling object.cljs will freeze LT as LT no longer has any objects defined. In the case of editor.cljs, if you comment the editor object type and do a file re-eval, you don't see errors. My suggestion is to stick to evaling forms when exploring LT and only do a file eval as you learn more of the codebase and understand the implications of a given file eval. I can add a brief description about this in the wiki or doc/for-committers.md if you think that'd be helpful to others. When reading LT's source you may come across a fn that doesn't have an obvious use and may appear toīe unused.
Do a LightTable user search for the given fn.git log -u -S WORD will do a code history search for WORD.įor example, to see where proc/exec is used.Doc window in lighttable pane sizel code#ĭoc window in lighttable pane sizel code#.Doc window in lighttable pane sizel update#.Doc window in lighttable pane sizel install#.
0 kommentar(er)
