Repository navigation
Conversation
TheCelavi
force-pushed
the
bugfix/issue-1
branch
from
October 7, 2026 17:19
758f81d to
6dd1593
Compare
This was referenced Oct 7, 2026
Closed
TheCelavi
force-pushed
the
bugfix/issue-1
branch
from
October 7, 2026 17:29
6dd1593 to
4a55dde
Compare
Bumping patch version, can be deployed. Bumping patch version, can be deployed.
TheCelavi
force-pushed
the
bugfix/issue-1
branch
from
October 8, 2026 06:33
4a55dde to
6ad9e8e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not the prettiest solution, but I do not have any idea how to modify configuration depending on if this is test/dev or production build. Either way, this solves the issue, but it would be nice that there is some flag to check if it is a prod or dev/test build and depending on that to utilise proper tsconfig.json file.