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
I understand bs-platform is intended to be installed globally, but it unnecessarily vendors in a bunch of OCaml tooling I already have for my other projects (relevant, of course, is #404: BSB / Reason with existing OCaml setup / Merlin is underdocumented); and there's no way to install justbsc and bsb (this project badly needs some refactoring/modularization! I should, ideally, just be able to npm install --save-dev bs-compiler bs-build-system, and not deal with any of this, y'know?)
So, anyway, for this Issue, bsb -init ./ should more gracefully handle existing filesystem contents when initializing the current directory. Especially given that, if you install bs-platform for a single project or just to experiment with it, this means bsb -init is going to wipe out bsb itself.
The workaround, obviously, if anybody else runs into this before a fix is landed, is to install bsb in an adjacent directory and/or globally, and then bsb -init your_project from scratch.
The text was updated successfully, but these errors were encountered:
Welp.
I understand
bs-platform
is intended to be installed globally, but it unnecessarily vendors in a bunch of OCaml tooling I already have for my other projects (relevant, of course, is #404: BSB / Reason with existing OCaml setup / Merlin is underdocumented); and there's no way to install justbsc
andbsb
(this project badly needs some refactoring/modularization! I should, ideally, just be able tonpm install --save-dev bs-compiler bs-build-system
, and not deal with any of this, y'know?)So, anyway, for this Issue,
bsb -init ./
should more gracefully handle existing filesystem contents when initializing the current directory. Especially given that, if you installbs-platform
for a single project or just to experiment with it, this meansbsb -init
is going to wipe outbsb
itself.The workaround, obviously, if anybody else runs into this before a fix is landed, is to install bsb in an adjacent directory and/or globally, and then
bsb -init your_project
from scratch.The text was updated successfully, but these errors were encountered: