gasilkingdom.blogg.se - Lighttable clojurescript node.js

#LIGHTTABLE CLOJURESCRIPT NODE.JS MAC OS X#
#LIGHTTABLE CLOJURESCRIPT NODE.JS INSTALL#
#LIGHTTABLE CLOJURESCRIPT NODE.JS UPDATE#
#LIGHTTABLE CLOJURESCRIPT NODE.JS UPGRADE#

Honestly it’s an amazing euphemism for “for killing Atom” so I’m not going to bother to sweet-coat anything: in fact this post will probably have some harsh words, so if you like Microsoft (for some reason) I advise you to stop reading…Īnyway: Microsoft is a shitty piece of crap company.

#LIGHTTABLE CLOJURESCRIPT NODE.JS UPGRADE#

This will be noise we have to live with until we upgrade ClojureScript.So, Microsoft blogger decided to post about “sunsetting Atom”. WARNING: Use of undeclared Var re/seq at line 197. Make sure there are no pending git changes as this script will change git branches and push generated api docs to gh-pages.Įxpect to see a ton of warnings e.g.

Run script/build-api-docs.sh on a clean git state.

This step will be removed once there is upstream support for version in :source-uri

In project.clj make sure that points to current LT version.

To build api documentation for current LT version and publish generated docs:

After release, build api documentation.

Mailing list announcement - example email.

Publish GH release which creates git tag and notifies users about new release.

#LIGHTTABLE CLOJURESCRIPT NODE.JS MAC OS X#

Run openssl md5 lighttable-x.y. on Mac OS X or Linux.Run certUtil -hashfile lighttable-x.y.z-windows.zip MD5 on Windows.Generate an MD5 checksum for the binary package:.Upload binaries from script/build.sh -release to draft.Each core developer should QA at least one OS using the QA checklist.Add changelog for release to CHANGELOG.md.Make sure plugin versions in script/build.sh are latest versions.Make sure electron version is up to date in version.json.

#LIGHTTABLE CLOJURESCRIPT NODE.JS UPDATE#

Update deploy/core/package.json, deploy/core/version.json and project.clj (including the Codox :source-uri value) to 0.X.X.This is our release checklist which can be dropped in to an issue: This background thread is invoked with the background macro. cljsDeps.js is used by threadworker.js to run javascript in a background thread. When upgrading ClojureScript, cljsDeps.js needs to be rebuilt with lein cljsbuild once cljsdeps. git log -u -S WORD will do a code history search for WORD.For example, to see where proc/exec is used Do a LightTable user search for the given fn.When reading LT's source you may come across a fn that doesn't have an obvious use and may appear to be unused. Namespaces that the console ns depend on cannot refer to the clojure var but can refer to the js fn e.g. Catch blocks should log errors with lt.nsole/error.Catch blocks should catch on :default unless there is a specific exception to be caught.lighttable - Mostly lighttable js libs except for lighttable/util/ which should be moved to vendored dependencies.Īllows us to build cross platfrom desktop apps.

codemirror_addons - Provides codemirror addons.

Some of them differ slightly from the original e.g.

These should eventually become vendored dependencies.

These packages have had custom commits that should get sent upstream.

Forked dependencies are "forkedDependencies" in package.json.

Dependencies should not be updated without good QA and checking the dependency's changelog.

#LIGHTTABLE CLOJURESCRIPT NODE.JS INSTALL#

npm install To see outdated dependencies: npm outdated.

To update an individual dependency: cd deploy/core & npm install e.g.

These are dependencies that should not be modified and should be updated with upstream versions.

Vendored dependencies are "dependencies" in package.json.This directory is currently a mix of vendored dependencies, forked dependencies and Light Table specific libraries: Node dependencies are at deploy/core/node_modules/. Node package installs last done with node.js v2.5.0 and npm v2.13.2. Mousetrap for handling keyboard shortcuts.Current ClojureScript version and libraries we use are in project.clj.