-
Notifications
You must be signed in to change notification settings - Fork 1
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
3 publish blog #6
Conversation
Don't build links with "skohub-blog" prefix as these would result in adding that path to our publish site. As we use a subdomain "blog.skohub.io" we don't want to need this.
@katauber see my own code comment where I asked about advice and: the |
I think the size itself is no problem but what I don't understand why it is so much bigger than before (from ~ 21000 lines to 46000 lines). Maybe the reason is that I use lockfile version 1 (npm v6) and you used lockfile version 2 (npm v7), see https://stackoverflow.com/questions/11414392/git-diff-thinks-the-last-line-of-the-file-has-been-moved-after-the-end-of-file. If that is the reason I think it's ok. I will update my npm version to v7 and see what happens with the package-lock.json. |
The cause of the huge package-json.lock seems indeed because of lockfile version 2. |
Sorry, I wanted to link this url https://docs.npmjs.com/cli/v7/configuring-npm/package-lock-json#lockfileversion in my last comment. That makes more sense.
👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the different npm versions result in different package-lock.json files, there should a recommendation of npm version (7?) in the README.
This config file of format rules can be applied by many IDEs and editors, e.g. codium and vim. Some need an extra plugin for that, like the latter.
There is already a note in the README ( |
Publish under root level.
See #3.