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
Grunt, for example, has tasks for concatenating and minifying JavaScript. The UglifyJS dependency isn't stated until you run make, which will probably confuse contributors. Alternatively, we could just add aight to npm and add uglify-js to devDependencies in the package.json.
The text was updated successfully, but these errors were encountered:
While building the module I faced an issue, that is in .gitmodules file all the git links are given in git@github.com style, which gave me the error Permission denied (publickey). I had to manually change the git links to https to make it work. Is this (git@github) needed for this project exclusively? If so, contributors have to manually change .gitmodules every time they contribute?
As for the build process, you can also look into Gulp too, which has streaming build system consisting of tasks which is more convenient in my opinion.
I'm pretty happy with what we've got in v2. We've got a package.json now (but haven't registered with npm yet), so you need to install the dev dependencies first:
$ npm install
Then, you can run either of these commands to rebuild aight.js and aight.min.js:
$ npm run build
# or
$ make clean all
Running npm run watch will start watchy on the src and lib dirs and the Makefile, so that any changes to those files will trigger a rebuild.
Grunt, for example, has tasks for concatenating and minifying JavaScript. The UglifyJS dependency isn't stated until you run
make
, which will probably confuse contributors. Alternatively, we could just add aight to npm and adduglify-js
todevDependencies
in the package.json.The text was updated successfully, but these errors were encountered: