推荐 最新
周舟莫UI设计

Prettier 配置文件写成.prettierrc.js不生效是什么原因?

保存格式化prettier格式化配置没有生效?.prettierrc.js没有生效,但是配置文件要是写成".prettierrc"或者".prettierrc.json" json格式就能被读取并生效,这是啥问题呢? 设置步骤如下 1. 添加prettier配置文件 2. formatOnSave: true 如果我prettier配置文件是json格式的,是能读到项目的prettier配置项并格式化生效 "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20241014/399eac3fe60c9afb928a0f97763cf61f.png)格式化也正确 但是如果我写的是".prettierrc.js" 时候,对应的配置项目好像没有被读取到(或者是被默认的覆盖了?) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20241014/19ddb1e1e0f38694b276af2c78bbd04d.png) 可以看到读取配置并不是".prettierrc.js"的配置项而是全局设置的默认项。 这大概会是什么原因呢? package.json如下 { "name": "nodejs-koa2-blog", "version": "1.0.0", "description": "基于 Node.js Koa2 实战开发的一套完整的博客项目网站,使用 Koa2 二次开发一套适合多端的 RESTful API,同时配套完整的后台管理系统,且前端展示既有基于 ejs 服务端渲染,也有基于 Vue.js 前后端分离的 2 套前端网站。", "main": "index.js", "scripts": { "dev": "nodemon app.js", "test": "jest _tests --forceExit --runInBand --colors" }, "repository": { "type": "git", "url": "git+https://github.com/liangfengbo/nodejs-koa2-blog.git" }, "keywords": [ "nodejs", "koa2", "sequelize", "mysql", "ejs", "vuejs", "JavaScript", "博客网站", "Node.js实战", "ejs 服务端渲染" ], "author": "Fengbo Liang, https://github.com/lfb", "license": "ISC", "bugs": { "url": "https://github.com/lfb/nodejs-koa2-blog/issues" }, "_moduleAliases": { "@": ".", "@app": "app", "@core": "core", "@middlewares": "middlewares", "@api": "app/api", "@dao": "app/dao", "@lib": "app/lib", "@models": "app/models", "@service": "app/service", "@validators": "app/validators" }, "homepage": "https://github.com/lfb/nodejs-koa2-blog#readme", "dependencies": { "@koa/cors": "^3.0.0", "basic-auth": "^2.0.1", "bcryptjs": "^2.4.3", "ejs": "^3.1.8", "hashids": "^2.1.0", "highlight.js": "^11.1.0", "jest": "^24.9.0", "jsonwebtoken": "^8.4.0", "koa": "^2.7.0", "koa-bodyparser": "^4.2.1", "koa-ratelimit": "^5.0.1", "koa-router": "^7.4.0", "koa-static": "^5.0.0", "koa-views": "^8.0.0", "markdown-it": "^12.1.0", "module-alias": "^2.2.2", "moment": "^2.24.0", "mysql2": "^2.2.5", "nodemon": "^2.0.12", "npm-check": "^5.9.0", "qiniu": "^7.4.0", "require-directory": "^2.1.1", "sequelize": "^6.6.5", "supertest": "^4.0.2", "validator": "^10.11.0", "xss": "^1.0.6" }, "directories": { "test": "_tests" }, "devDependencies": { "eslint": "^8.56.0", "eslint-config-prettier": "^9.1.0", "prettier": "3.2.4" } }

0
1
0
浏览量207
周舟莫UI设计

如何解决Nginx HTTPS配置访问失败问题?

配置HTTP成功,并且所有网页皆可访问。唯独HTTPS失败,我的nginx配置文件如下 user www-data; worker_processes auto; pid /run/nginx.pid; include /etc/nginx/modules-enabled/*.conf; events { worker_connections 768; # multi_accept on; } http { sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; include /etc/nginx/mime.types; default_type application/octet-stream; server{ listen 443 ssl; server_name www.xiaoyangst.top; ssl_certificate /home/xyst/XrtcDemo/server/cert/www.xiaoyangst.top_cert_chain.pem; ssl_certificate_key /home/xyst/XrtcDemo/server/cert/www.xiaoyangst.top_key.key; location / { proxy_pass https://www.xiaoyangst.top:8443; } } server { listen 80; server_name www.xiaoyangst.top; root /home/xyst/XrtcDemo/myapp/build; index index.html; location / { try_files $uri %uri/ /index.html; } location /api { proxy_pass http://www.xiaoyangst.top:8888; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } return 301 https://$server_name$request_uri; } ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE ssl_prefer_server_ciphers on; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; gzip on; include /etc/nginx/conf.d/*.conf; include /etc/nginx/sites-enabled/*; } 访问情况 "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240929/3ab4ae1639a620dde6c35635fd870882.png) 通过 openssl s_client -connect www.xiaoyangst.top:443 命令确保SSL和证书没有问题 后端Node.js服务正常启动,且通过PostMan工具测试后端没有问题。所以问题应该在nginx这边 "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240929/a6f3ce6feb2cc74e5459f0b476a5d60b.png) "image.png" (https://wmprod.oss-cn-shanghai.aliyuncs.com/c/user/20240929/f3065e6589b5b025b66e7102b5b00104.png) 我怀疑是没有把资源给到HTTPS,所以我把HTTP去掉,直接给到HTTPS server{ listen 443 ssl; server_name www.xiaoyangst.top; ssl_certificate /home/xyst/XrtcDemo/server/cert/www.xiaoyangst.top_cert_chain.pem; ssl_certificate_key /home/xyst/XrtcDemo/server/cert/www.xiaoyangst.top_key.key; server_name www.xiaoyangst.top; root /home/xyst/XrtcDemo/myapp/build; index index.html; location / { try_files $uri %uri/ /index.html; } location /api { proxy_pass https://www.xiaoyangst.top:8443; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } 问题得到解决,但是我想说如何既可以配置HTTP,还可以配置HTTPS呢? 就是访问HTTP可以成功,访问HTTPS也可以成功,难道只能选择再Copy一份吗?(因为不很熟悉nginx)

0
1
0
浏览量207
D_Y_大师

关于vite插件开发中如何访问.ts文件?

咨询一个vite插件开发的问题。 首先说一下需求背景,我想做一个插件,能够让使用插件的人能够快速初始化一个比较完善的基于vue的后台脚手架。目前卡在vite插件的config生命周期中。我想定义一个专门的配置文件xxx.config.ts文件。然后在vite插件的config生命周期中访问这个配置文件,让它的配置和vite的配置进行部分合并。但是我发现使用import(process.cwd() + '/xxxx.config.ts')的话会因为.ts文件无法被解析而报错。 无奈之下,尝试使用fs模块去访问对应的配置文件,然后复制出一个一摸一样的.js文件,然后通过improt访问这个.js文件就能行了。但是这样又出现一个问题。在使用这个插件的项目运行打包操作的时候,又会警告[plugin:vite:resolve] Module "fs" has been externalized for browser compatibility。不知道如何解决。 其实想类似unocss这类库一样。unocss.config.ts也能正常读取。请问他们是如何实现的。有大佬能提供一下思路么? 为什么不直接使用xxx.config.js呢。因为ts有较好的错误检测和提示。 期望能够正常读取.ts文件 简单说就是,我写了一个vite插件,但是这个插件支持用户自定义配置内容。然后我想着在插件中调用fs模块去获取用户当前项目的这个配置文件。但是使用我插件的项目在打包的时候会警告。说Module "fs" has been externalized for browser compatibility.请问要如何解决!!

0
1
0
浏览量121