-
Notifications
You must be signed in to change notification settings - Fork 402
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
公告:1.13.4 的问题说明 #613
Comments
错误版本是通过npm-check-updates获取的版本号 |
cnpm 有办法规避么(刚试了好像cnpm还是有问题)? |
很多项目可能不会粗暴的直接 ^1,或者直接1.x。 |
@wufeng87 一般cnpm的更新可能不会那么及时 |
可以考虑发个1.13.5来覆盖?这样就保证不会出现问题了 |
cnpm 也是 1.13.3。 $ cnpm i babel-plugin-import
✔ Installed 1 packages
✔ Linked 7 latest versions
✔ Run 0 scripts
✔ All packages installed (7 packages installed from npm registry, used 290ms(network 289ms), speed 193.64KB/s, json 7(55.96KB), tarball 0B)
$ cat node_modules/babel-plugin-import/package.json
{
"name": "babel-plugin-import",
"version": "1.13.3", |
@zhangyuang 打包脚本的 bug 还没时间排查,需要看下为啥会出现本地路径。 |
在 yarn v1.x 没有问题 安装的是 1.13.3 但在 yarn v3.2 安装的 1.13.4 |
@sorrycc 之前在用gulp打包的时候,有.babelrc之类的文件,打包的时候对于babel插件的参数,遇到过configFile参数会造成出现这种绝对路径的问题。可以检查下是否是这个原因。 |
大佬简单粗暴了,近期项目 全部构建失败了。 |
兄弟们,锁1.12.0版本就可以了 |
@mizi-lin 这是有本地的缓存吧。 |
特意清了缓存 测试的· |
@mizi-lin 全局缓存也清了? |
介于有多个 issue,统一说明下。
1.13.4 有问题,2022.4.11 中午发现有问题时,已通过 dist-tag 设置 latest 回 1.13.3。
正常来说,npm install babel-plugin-import@^1 不会安装到错误的版本。
$ npm i babel-plugin-import@^1 Packages: +7 +++++++ Packages are hard linked from the content-addressable store to the virtual store. Content-addressable store is at: /Users/chencheng/.pnpm-store/v3 Virtual store is at: node_modules/.pnpm Progress: resolved 7, reused 7, downloaded 0, added 7, done dependencies: + babel-plugin-import 1.13.3
所以,不清楚大家怎么会安装到错误的版本。如果还有遇到,建议做两个尝试,
1、删除 node_modules(如果有 yarn.lock、package-lock.json、pnpm-lock.yarml,请一并删除)并重装
2、检查本地或 npm mirror(如有)的缓存情况
The text was updated successfully, but these errors were encountered: