make css generate a different package-lock.json on master #3343

New Issue

GiteaMirror · 2025-11-02T05:09:15-06:00

GiteaMirror commented

2025-11-02 05:09:15 -06:00

Originally created by @lunny on GitHub (May 16, 2019).

Don't know if this is related with #6952

$ make css
npx lesshint public/less/
npx lessc --clean-css="--s0 -b" public/less/index.less public/css/index.css
npx lessc --clean-css="--s0 -b" public/less/themes/arc-green.less > public/css/theme-arc-green.css;
npx postcss --use autoprefixer --no-map --replace public/css/*

/Volumes/data/Projects/gitea/gitea on  master! ⌚ 20:08:29
$ ls
BSDmakefile       Dockerfile        README.md         contrib           docker            go.sum            main.go           options           routers           templates
CHANGELOG.md      LICENSE           README_ZH.md      coverage.out      docs              indexers          models            package-lock.json scripts           vendor
CONTRIBUTING.md   MAINTAINERS       assets            custom            gitea             integrations      modules           package.json      snap
DCO               Makefile          cmd               data              go.mod            log               node_modules      public            sqlite-log

/Volumes/data/Projects/gitea/gitea on  master! ⌚ 20:08:32
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   package-lock.json

no changes added to commit (use "git add" and/or "git commit -a")

Originally created by @lunny on GitHub (May 16, 2019). Don't know if this is related with #6952 ``` $ make css npx lesshint public/less/ npx lessc --clean-css="--s0 -b" public/less/index.less public/css/index.css npx lessc --clean-css="--s0 -b" public/less/themes/arc-green.less > public/css/theme-arc-green.css; npx postcss --use autoprefixer --no-map --replace public/css/* /Volumes/data/Projects/gitea/gitea on  master! ⌚ 20:08:29 $ ls BSDmakefile Dockerfile README.md contrib docker go.sum main.go options routers templates CHANGELOG.md LICENSE README_ZH.md coverage.out docs indexers models package-lock.json scripts vendor CONTRIBUTING.md MAINTAINERS assets custom gitea integrations modules package.json snap DCO Makefile cmd data go.mod log node_modules public sqlite-log /Volumes/data/Projects/gitea/gitea on  master! ⌚ 20:08:32 $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: package-lock.json no changes added to commit (use "git add" and/or "git commit -a") ```

GiteaMirror added the topic/build label 2025-11-02 05:09:15 -06:00

GiteaMirror closed this issue

2025-11-02 05:09:15 -06:00

GiteaMirror commented

2025-11-02 05:09:15 -06:00

@silverwind commented on GitHub (May 16, 2019):

make css can itself not generate package-lock.json, only npm install can. I think what you're seeing is that you are on a different version of npm which writes a different lockfile.

Generally, I think it's best to actually remove package-lock.json from git, it's purpose is rather questionable in my point of view. Will get a PR up for this later.

@silverwind commented on GitHub (May 16, 2019): `make css` can itself not generate `package-lock.json`, only `npm install` can. I think what you're seeing is that you are on a different version of `npm` which writes a different lockfile. Generally, I think it's best to actually remove `package-lock.json` from git, it's purpose is rather questionable in my point of view. Will get a PR up for this later.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3343

make css generate a different package-lock.json on master #3343

`make css` generate a different `package-lock.json` on master #3343