-
Notifications
You must be signed in to change notification settings - Fork 30
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
"Manifest must include a JSON object." #19
Comments
@gregfenton it appears it lacks support for app.config.js: #12 . It's a great library but I had to shelve use of it due to lack of support for app.config.js. |
A possible workaround is to use app.json and app.config.js. Example: app.json:
app.config.js:
There are actually other tools that don't play nice with app.config.js (e.g., detox) |
@oriharel - interesting, though then I wonder the value of using this extension over pure standard-version? I have essentially followed your approach, though I named my file
|
I need this feature too... |
Having this feature would be helpful |
Note: |
Yeah that's a bummer but I think it's famous enough to get a serious fork. |
Topic and scope of discussion
Unable to get version bumping for
app.config.js
files - getting the subject's message to the console.Motivation
To understand if a flexible, dynamic configuration is currently possible.
Additional context
In my
.versionrc.js
I have the following:When I run
npx standard-version --dry-run
I get the following output:and my
app.config.js
files do not update. I have 2 app.config.js files (I have 2 customer-configs), and I'm quite certain that the 6 instances of "Manifest must include a JSON object." are coming from (2 customer-configs * 3 updaters).Looking at the code in
standard-version-expo/build/expo.js
, it seems that the code toparseJsonString()
is failing with the exception message ending with:So it is blowing up simply trying to read in the app.config.js.
Any thoughts on what I could try next? It clearly finds the config files, but fails to parse them
The text was updated successfully, but these errors were encountered: