-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider removing settings builder as a local dep #23
Comments
(cross-posted from Dd #programs for transparency): So what this means in practice is that you only have to install This would differ from one of the current workflows, which involves installing This latter workflow involves more steps (and requires internet access to download all of the dependencies if they haven't been set up already as we had to do recently), but does give more leverage for any specific build specs that were written into the config (such as language localization choice I believe). However I don't know how many configs are using this currently. For all the ones I've built, they've been clones of the default config with no changes made to the build script. So that could be the norm and the global |
(also cross-posted from Dd #programs): for programs side, i guess the question boils down to choosing between which workflow is easier to understand/use by default:
or
|
Stemmed from a conversation with @rudokemper while doing some debugging work on
mapeo-settings-builder
. Based on programs usage, there's no consensus on how the build step is done i.e. via the local npm run script command (npm run build
) or using a globally installed executablemapeo-settings ...
. Documentation seems to be somewhat conflicting as well.Seems like defaulting to using a global install would require less technical overhead for end-users (less of a need to understand node/npm intricacies), but it comes at the cost of some customization regarding the version of the builder you use (e.g. maybe a more recent version of the executable isn't compatible with the project being worked on).
Wanted to bring this up for discussion and see if there are any additional thoughts on it
@gmaclennan
The text was updated successfully, but these errors were encountered: