Closed sanak closed 1 year ago
I apologize for the delay in noticing the issue. I've acknowledged the problem and will work on the fix.
@sanak
https://github.com/farend/redmine_theme_farend_bleuclair/pull/67 I've created a pull request. Would you be so kind to check if it works without errors in your environment? I truly appreciate your help.
Okay, I will take a look at the PR at tonight or tomorrow. Thanks a lot ! 🙇
@ishikawa999 Thanks! I confirmed the followings on my local environment (M1 Mac, OS: Ventura 13.5.2, Node.js: 18.17.1).
npm install
again is disappearednpm run build
generated minified js/css files are same with the branch The followings are both tiny things and ignorable, but I noticed from further check, so just for your information.
npm audit fix
seems to be safe.
2 vulnerabilities (1 low, 1 moderate)
after executing npm install
, so I tried to execute npm audit fix
and the npm run build
generated minified js/css files are same with the branch. (Just package-lock.json
was updated.)CSS color minification can be off from webpack config setting.
I checked minified theme.css
diff in the PR by replacing \}
to \}\n
with regexp, and noticed that 1 color expression was changed from rgba
to hsla
. (Other changes seem to be just correct sort order.)
Disabling cssnano colormin to minimizerOptions keeps the original color, but it also keeps original transparent
.
Result (update) diff:
@sanak Thanks for the feedback. I have changed the colormin settings https://github.com/farend/redmine_theme_farend_bleuclair/pull/67/commits/d9ff20bc77ab7e96aee4b6a1fe0f9e88ee572f59
Pull requests merged.
Recently (at 2023-09-11), Node.js 16 became EOL (https://endoflife.date/nodejs), so I upgraded my local environment Node.js version to 18 LTS latest (18.17.1) from asdf package manager.
But in that environment, I noticed that
package-lock.json
has many differences when executingnpm install
,and executing
npm install
again shows the following error.I guess that something updating webpack and loaders seems to be necessary, but I am not familiar with webpack and loaders related things, so checking Node.js 18 environment is really helpful. 🙇🙏 (Note that I encountered the similar error in Node.js 16 (16.20.2) environment, but Node.js 14 (14.21.3) environment was no problem.)