npm发包失败，直接报错：

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/react-native-use-toast - You do not have permission to publish "react-native-use-toast". Are you logged in as the correct user?
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

最新版0.76.3报错 …

这个具体的报错信息没给，参考

https://github.com/facebook/react-native/issues/34189

Debugging this issue on my M1 mac, I discovered that I had never set my git config to use the correct line endings for *nix on macOS. UPDATE: I had actually forgotten to unset them after working with a repo with Windows line endings. This means they were set to git config --global core.autocrlf true which is the setting for windows.

This is the correct setting for linux/mac.

git config --global core.autocrlf input

You can also unset them and use the default which is false

git config --global --unset core.autocrlf

After this, you will need to normalize all the line endings in the project (unless you want to re-clone).

https://stackoverflow.com/a/13154031

After you have done the configuration, you might want git to normalize all the files in the repo. To do this, go to to the root of your repo and run these commands:

git rm --cached -rf .
git diff --cached --name-only -z | xargs -n 50 -0 git add -f

If you now want git to also normalize the files in your working directory, run these commands:

git ls-files -z | xargs -0 rm
git checkout .

There are some .bat files for windows that you will not want to change, so discard those.

Once you have done these steps, you shouldn’t need any of the custom workarounds in this thread.

Originally posted by @shwanton in https://github.com/facebook/react-native/issues/34189#issuecomment-1502532287

如果想修改已经推送到远程的 Git 提交信息，可以使用 git rebase 和 git commit –amend 来更改提交历史。修改已经推送的提交信息是有风险的，特别是如果其他人已经拉取了你的提交历史。修改历史后，可能会导致他们的工作分叉，因此在多人协作时要小心使用。

Vue 里面，加载本地图片，:src=””直接写成变量是不行的 …

演示网址：https://vue.cctv3.net/#/dynamicPathAsSrc

我就想问问，中国程序员去日本当程序员容易吗？

这种场景比较常见，很多买保险的页面，什么合同页面都是这么搞的，我滑动到底才能点下一步

演示网址：https://vue.cctv3.net/#/hasReadHTML

Vue里面很有多蛋疼的地方，比如提交表单的时候，移动端和桌面端是两套 UI，但是操作的逻辑是一样的。尤其是比如表单是分步骤的，还得处理多个步骤，所以说得把业务封装成hooks，两个端都能复用。

比较蛋疼的地方：

• 多个hooks如何修改同一份store

• hooks如何引用组件的props

• hooks如何调用组件的emits

请直接看疗效 …

之前是采用middleware的方式，现在新版本的不适用了 …

重点就是想办法给response添加允许跨域的请求头 …

之前总结过，没解决根本问题，还是没有找到本地的什么配置，导致了 index.tsx 被忽略 …

最近电脑莫名其妙抽风了，新建什么文件都行，唯独index.tsx，死活检测不到文件变化，每次都要手动执行：

git add /src/.../index.tsx --force

我 TM 心态都要爆炸了 …