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
For our project, we are using browserify and brace, however, we would really like to use a different version of ace (in our github repo). Is there any way to edit the update.js script, or modify the npm package to change the exec('git clone git://github.com/ajaxorg/ace-builds.git ' + buildroot); command to exec('git clone git://github.com/gracelang/ace/fix-brackets/build ' + buildroot);? Cloning this repository and manually changing the url hasn't worked, since npm overwrites the "brace" directory, or throws an error due to it being a github repo. This issue is complicated by the fact that the npm build of brace does not include the build directory. If this isn't something that is feasible, or even possible — sorry for the extra issue!
The text was updated successfully, but these errors were encountered:
Sorry for the noise! The obvious solution that I missed, although not ideal, is to use a local copy of brace, change the url there (and some of the other exec() commands to get the correct folder). Then run the npm update command on the local copy, and change the npm dependency to the local copy. (Probably not possible with npm, but it would be awesome to have an option to link to another ace repo for brace.)
For our project, we are using browserify and brace, however, we would really like to use a different version of ace (in our github repo). Is there any way to edit the update.js script, or modify the npm package to change the
exec('git clone git://github.com/ajaxorg/ace-builds.git ' + buildroot);
command toexec('git clone git://github.com/gracelang/ace/fix-brackets/build ' + buildroot);
? Cloning this repository and manually changing the url hasn't worked, since npm overwrites the "brace" directory, or throws an error due to it being a github repo. This issue is complicated by the fact that the npm build ofbrace
does not include thebuild
directory. If this isn't something that is feasible, or even possible — sorry for the extra issue!The text was updated successfully, but these errors were encountered: