Open
Conversation
Signed-off-by: Nikolaos Karaolidis <nick@karaolidis.com>
Author
|
On a similar note, @lishid, should this lib be published or the changes upstreamed to avoid further issues with the prepare script, etc? If it does get published, we won't need package-lock.json after all. |
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
1 participant
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.
A lot of obsidian plugins use this repo directly as a source for cm-language:
https://github.com/lukeleppan/better-word-count/blob/master/package.json
https://github.com/blacksmithgu/obsidian-dataview/blob/master/package.json
https://github.com/Clemens-E/obsidian-languagetool-plugin/blob/master/package.json
Because the repo does not contain a package-lock.json, reproducible build systems fail. This commit simply adds a package-lock.json for latest main.