xiaohanyu 最近的时间轴更新 xiaohanyu 最近的时间轴更新 |
xiaohanyuV2EX 第 33155 号会员，加入于 2013-01-27 22:01:04 +08:00 |
xiaohanyu
| 调试健康：写给伏案工作者的健康指南小书 健康 • xiaohanyu • 19 天前 |
| PPResume 新年更新：新增两款简历模板
2 分享创造 • xiaohanyu • 21 天前 • 最后回复来自 xiaohanyu
|
8 |
| PPResume 更新： No Vendor Lock-in，对所有简历提供完整的 LaTeX 源代码
1 分享创造 • xiaohanyu • 38 天前 • 最后回复来自 JeremyFeng
|
2 |
| 写了篇关于 LaTeX/Typst/React-pdf 排版引擎的长文：《排版引擎纵谈：程序员的视角》
5 分享创造 • xiaohanyu • 80 天前 • 最后回复来自 xiaohanyu
|
15 |
| PPResume 更新： Pricing Plan 上线啦，本月注册享 50% 折扣 分享创造 • xiaohanyu • 78 天前 • 最后回复来自 onlytiancai | 4 |
| SaaS 产品集成 Stripe 支付的一些坑 Stripe • xiaohanyu • 99 天前 • 最后回复来自 xiaohanyu | 19 |
| PPResume 重大更新：支持中文（简体中文和繁体中文）简历了 分享创造 • xiaohanyu • 205 天前 • 最后回复来自 xiaohanyu | 9 |
| Safari 的 bug 真是茫茫多
1 Safari • xiaohanyu • 218 天前 • 最后回复来自 xiaohanyu
|
12 |
| PPResume 更新：优化性能，支持 PWA，作为一个 app 直接安装到系统中 分享创造 • xiaohanyu • 113 天前 • 最后回复来自 xiaohanyu | 2 |
xiaohanyu 最近回复了
7 天前 回复了 oldcai 创建的主题 › Stripe › Stripe 怎样收税比较简单？ |
除了切换成 MoR 这种，没什么特别好的办法。
网上有人说这种小 SaaS 除了在自己所在的国家 jurisdication 交交 sales tax ，别的可以不用管，有风险，但是不用 care 太多。
网上有人说这种小 SaaS 除了在自己所在的国家 jurisdication 交交 sales tax ，别的可以不用管，有风险，但是不用 care 太多。
7 天前 回复了 Cola98 创建的主题 › 程序员 › nextjs 正确使用方式 |
@superhot
我的项目架构 ( https://ppresume.com) 大概是这样的：
- ppresume
- packages/common
- packages/api
- packages/client
```sh
$ ls -l packages package.json pnpm-workspace.yaml pnpm-lock.yaml
-rw-r--r-- 1 hanyu staff 1485 Jan 14 21:09 package.json
-rw-r--r-- 1 hanyu staff 744184 Dec 30 10:49 pnpm-lock.yaml
-rw-r--r-- 1 hanyu staff 27 Jan 22 2024 pnpm-workspace.yaml
packages:
total 0
drwxr-xr-x 16 hanyu staff 512 Jan 14 21:09 api
drwxr-xr-x 24 hanyu staff 768 Jan 14 21:09 client
drwxr-xr-x 12 hanyu staff 384 Jan 14 21:09 common
```
- api: 后端 API
- client: 前端 next.js 实现
- common: 前后端共享的 data model/schema validation/utils 等等，不依赖 node.js 系统 API ，所以可以同时跑在两端上。
回复你的问题：
1. tsconfig 我没有特别配置过，common package 的 tsconfig:
```json
{
"compilerOptions": {
"esModuleInterop": true,
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
"moduleResolution": "node",
"resolveJsonModule": true,
"declaration": true,
"declarationMap": true,
"sourceMap": true,
"types": ["node", "jest"],
"importHelpers": true,
"composite": true,
"target": "es5",
"rootDir": "src",
"outDir": "dist",
"baseUrl": "."
},
"include": ["**/*.ts", "**/*.json"]
}
```
2. 把 common package 当成一个单独的 npm/pnpm 包引入 api/client ，不需要用嵌套路径。npm/pnpm/yarn 都有相应的 workspace 特性，我最开始用的是 yarn ，后来转到了 pnpm ，参考： https://pnpm.io/workspaces
我的 pnpm-workspace 配置：
```
packages:
- 'packages/*'
```
顶层 `package.json` 配置：
```
{
"name": "ppresume",
"private": true,
"version": "0.7.0",
"dependencies": {
"concurrently": "^8.2.1",
"husky": "^8.0.2",
"lint-staged": "^13.1.0",
"prettier": "^2.8.1"
},
"devDependencies": {
"@commitlint/cli": "^19.3.0",
"@commitlint/config-conventional": "^19.2.2",
"@trivago/prettier-plugin-sort-imports": "^4.0.0",
"commit-and-tag-version": "^12.4.0"
},
"lint-staged": {
"**/*": "prettier --write --ignore-unknown"
},
"resolutions": {
"jackspeak": "2.1.1"
},
"scripts": {
"api": "pnpm --filter api",
"common": "pnpm --filter common",
"coverage": "pnpm common build && concurrently --kill-others-on-fail \"pnpm common coverage\" \"pnpm client coverage\" \"pnpm api coverage\"",
"client": "pnpm --filter client",
"build": "pnpm common build && concurrently --kill-others-on-fail \"pnpm client build\" \"pnpm api build\"",
"dev": "pnpm common build && concurrently --kill-others-on-fail \"pnpm client dev\" \"pnpm api dev\"",
"start": "pnpm common build && concurrently --kill-others-on-fail \"pnpm client start\" \"pnpm api start\"",
"test": "pnpm common build && concurrently --kill-others-on-fail \"pnpm common test\" \"pnpm client test\" \"pnpm api test\"",
"release": "commit-and-tag-version --bumpFiles package.json packages/*/package.json",
"commitlint": "commitlint --edit"
},
"commit-and-tag-version": {
"writerOpts": {
"commitsSort": false
}
}
}
```
`common/package.json` 的配置：
```
{
"name": "common",
"version": "0.7.0",
"description": "common code shared by ppresume project",
"author": "Xiao Hanyu",
"private": true,
"devDependencies": {
"@types/jest": "^29.5.5",
"@types/lodash": "^4.14.202",
"@types/node": "^20.5.7",
"jest": "^29.7.0",
"ts-jest": "^29.1.1",
"typescript": "^5.2.2"
},
"main": "dist/index",
"types": "dist/index",
"scripts": {
"build": "tsc --build --force",
"coverage": "jest --coverage",
"test": "jest"
},
"dependencies": {
"escape-latex": "^1.2.0",
"tslib": "^2.6.2"
}
}
```
调用 `pnpm common build` 来完成 `common` package 的 build ，然后在 api/client 里直接 `import xxx from 'common'` 就可以了
3. mono-repo 有 mono-repo 的好处的，最大的好处是出了 regression 问题可以用 `git bisect` 找 bug ，commit log 的维护重点还是靠个人/团队守规则。
我个人项目的概况： https://x.com/hanyuxiao1988/status/1878625079829172510
以上
我的项目架构 ( https://ppresume.com) 大概是这样的：
- ppresume
- packages/common
- packages/api
- packages/client
```sh
$ ls -l packages package.json pnpm-workspace.yaml pnpm-lock.yaml
-rw-r--r-- 1 hanyu staff 1485 Jan 14 21:09 package.json
-rw-r--r-- 1 hanyu staff 744184 Dec 30 10:49 pnpm-lock.yaml
-rw-r--r-- 1 hanyu staff 27 Jan 22 2024 pnpm-workspace.yaml
packages:
total 0
drwxr-xr-x 16 hanyu staff 512 Jan 14 21:09 api
drwxr-xr-x 24 hanyu staff 768 Jan 14 21:09 client
drwxr-xr-x 12 hanyu staff 384 Jan 14 21:09 common
```
- api: 后端 API
- client: 前端 next.js 实现
- common: 前后端共享的 data model/schema validation/utils 等等，不依赖 node.js 系统 API ，所以可以同时跑在两端上。
回复你的问题：
1. tsconfig 我没有特别配置过，common package 的 tsconfig:
```json
{
"compilerOptions": {
"esModuleInterop": true,
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
"moduleResolution": "node",
"resolveJsonModule": true,
"declaration": true,
"declarationMap": true,
"sourceMap": true,
"types": ["node", "jest"],
"importHelpers": true,
"composite": true,
"target": "es5",
"rootDir": "src",
"outDir": "dist",
"baseUrl": "."
},
"include": ["**/*.ts", "**/*.json"]
}
```
2. 把 common package 当成一个单独的 npm/pnpm 包引入 api/client ，不需要用嵌套路径。npm/pnpm/yarn 都有相应的 workspace 特性，我最开始用的是 yarn ，后来转到了 pnpm ，参考： https://pnpm.io/workspaces
我的 pnpm-workspace 配置：
```
packages:
- 'packages/*'
```
顶层 `package.json` 配置：
```
{
"name": "ppresume",
"private": true,
"version": "0.7.0",
"dependencies": {
"concurrently": "^8.2.1",
"husky": "^8.0.2",
"lint-staged": "^13.1.0",
"prettier": "^2.8.1"
},
"devDependencies": {
"@commitlint/cli": "^19.3.0",
"@commitlint/config-conventional": "^19.2.2",
"@trivago/prettier-plugin-sort-imports": "^4.0.0",
"commit-and-tag-version": "^12.4.0"
},
"lint-staged": {
"**/*": "prettier --write --ignore-unknown"
},
"resolutions": {
"jackspeak": "2.1.1"
},
"scripts": {
"api": "pnpm --filter api",
"common": "pnpm --filter common",
"coverage": "pnpm common build && concurrently --kill-others-on-fail \"pnpm common coverage\" \"pnpm client coverage\" \"pnpm api coverage\"",
"client": "pnpm --filter client",
"build": "pnpm common build && concurrently --kill-others-on-fail \"pnpm client build\" \"pnpm api build\"",
"dev": "pnpm common build && concurrently --kill-others-on-fail \"pnpm client dev\" \"pnpm api dev\"",
"start": "pnpm common build && concurrently --kill-others-on-fail \"pnpm client start\" \"pnpm api start\"",
"test": "pnpm common build && concurrently --kill-others-on-fail \"pnpm common test\" \"pnpm client test\" \"pnpm api test\"",
"release": "commit-and-tag-version --bumpFiles package.json packages/*/package.json",
"commitlint": "commitlint --edit"
},
"commit-and-tag-version": {
"writerOpts": {
"commitsSort": false
}
}
}
```
`common/package.json` 的配置：
```
{
"name": "common",
"version": "0.7.0",
"description": "common code shared by ppresume project",
"author": "Xiao Hanyu",
"private": true,
"devDependencies": {
"@types/jest": "^29.5.5",
"@types/lodash": "^4.14.202",
"@types/node": "^20.5.7",
"jest": "^29.7.0",
"ts-jest": "^29.1.1",
"typescript": "^5.2.2"
},
"main": "dist/index",
"types": "dist/index",
"scripts": {
"build": "tsc --build --force",
"coverage": "jest --coverage",
"test": "jest"
},
"dependencies": {
"escape-latex": "^1.2.0",
"tslib": "^2.6.2"
}
}
```
调用 `pnpm common build` 来完成 `common` package 的 build ，然后在 api/client 里直接 `import xxx from 'common'` 就可以了
3. mono-repo 有 mono-repo 的好处的，最大的好处是出了 regression 问题可以用 `git bisect` 找 bug ，commit log 的维护重点还是靠个人/团队守规则。
我个人项目的概况： https://x.com/hanyuxiao1988/status/1878625079829172510
以上
21 天前 回复了 xiaohanyu 创建的主题 › 分享创造 › PPResume 新年更新：新增两款简历模板 |
@sikex 收到收到，太感谢了，bug 报告很详细。
22 天前 回复了 xiaohanyu 创建的主题 › 分享创造 › PPResume 新年更新：新增两款简历模板 |
@anUglyDog 嗯，有时候颜值就是正义么，哈哈
22 天前 回复了 xiaohanyu 创建的主题 › 分享创造 › PPResume 新年更新：新增两款简历模板 |
@scienhub 嗯，仁兄是懂行的哈
22 天前 回复了 xiaohanyu 创建的主题 › 分享创造 › PPResume 新年更新：新增两款简历模板 |
@scienhub 排版引擎是 LaTeX 呢，具体来说是 XeLaTeX 引擎，前两个月写了篇关于排版引擎技术选型的文章： https://blog.ppresume.com/posts/zh-CN/on-typesetting-engines ，供参考哈。
中文排版也是完全支持的，而且支持简体中文、繁体中文（香港）和繁体中文（台湾）三种，具体可以看：
- blog: https://blog.ppresume.com/posts/multi-languagues-support
- doc: https://docs.ppresume.com/content/multi-languages
中文排版也是完全支持的，而且支持简体中文、繁体中文（香港）和繁体中文（台湾）三种，具体可以看：
- blog: https://blog.ppresume.com/posts/multi-languagues-support
- doc: https://docs.ppresume.com/content/multi-languages
40 天前 回复了 wincatcher 创建的主题 › 分享创造 › [网站自荐] "WebSpy.Site" - 专业一站式网站流量分析及工具集成平台，深入分析网站流量数据，生成高颜值多维度分析报告。创新的工具坞设计，一键使用多种工具分析当前域名，让您的网站信息获取更轻松高效 |
@wincatcher 加油加油
40 天前 回复了 wincatcher 创建的主题 › 分享创造 › [网站自荐] "WebSpy.Site" - 专业一站式网站流量分析及工具集成平台，深入分析网站流量数据，生成高颜值多维度分析报告。创新的工具坞设计，一键使用多种工具分析当前域名，让您的网站信息获取更轻松高效 |
试验了下，挺不错的，是有打算做成类似于 similarweb 这样的工具平台么？有商业化计划么？
40 天前 回复了 wincatcher 创建的主题 › 分享创造 › [网站自荐] "WebSpy.Site" - 专业一站式网站流量分析及工具集成平台，深入分析网站流量数据，生成高颜值多维度分析报告。创新的工具坞设计，一键使用多种工具分析当前域名，让您的网站信息获取更轻松高效 |
问一下，网站数据是从哪里分析出来的呀？
62 天前 回复了 rexue123 创建的主题 › Stripe › paddle 收款域名审核，域名审核被拒，这是什么玩意呢 |
@realpg 你这人真是搞笑了咧，我哪里自说自话了？你怎么知道我没跟 paddle 的真人联系啊？为了开个户我还得订机票远涉重洋去找他们线下谈？你找他们线下谈他们就能接受么？
我邮件跟他们谈过几轮，贴几段原文：
```
Hi Hanyu,
I completely understand that you have registered your company recently and therefore you do not have the processing statements required.
However as a company, Paddle prioritises the safety and security of our valued customers, and this information is necessary for us to ensure a secure environment for all.
As we are unable to support your business at this time, I would recommend using an alternative payment provider until you are able to provide the requested processing statements.
I assure you that once you are able to resubmit your domain with the necessary information, our team will be more than happy to reassess the situation and provide a prompt response.
I appreciate your understanding.
```
```
Hi Hanyu,
I understand the challenge you're facing. To clarify, you will need to provide processing statements from a payment processor for at least the past three months. These statements help us assess your transaction history and ensure everything aligns with our requirements.
Yes, it typically means that you’ll need to integrate with another payment processor and generate some transaction history before applying for Paddle. Once you’re approved by Paddle, you can then migrate your customer data to our platform.
If you have any more questions or need further assistance during this process, please feel free to reach out.
```
人家已经写了：“Yes, it typically means that you’ll need to integrate with another payment processor and generate some transaction history before applying for Paddle. ”，但是这条规则就没在 paddle 的官网上明示过。
问题是，如果我已经集成了一个 payment processor ，我干嘛还要再费那个劲迁移到 paddle 啊？ MoR 的服务又不只 paddle 一家。
我邮件跟他们谈过几轮，贴几段原文：
```
Hi Hanyu,
I completely understand that you have registered your company recently and therefore you do not have the processing statements required.
However as a company, Paddle prioritises the safety and security of our valued customers, and this information is necessary for us to ensure a secure environment for all.
As we are unable to support your business at this time, I would recommend using an alternative payment provider until you are able to provide the requested processing statements.
I assure you that once you are able to resubmit your domain with the necessary information, our team will be more than happy to reassess the situation and provide a prompt response.
I appreciate your understanding.
```
```
Hi Hanyu,
I understand the challenge you're facing. To clarify, you will need to provide processing statements from a payment processor for at least the past three months. These statements help us assess your transaction history and ensure everything aligns with our requirements.
Yes, it typically means that you’ll need to integrate with another payment processor and generate some transaction history before applying for Paddle. Once you’re approved by Paddle, you can then migrate your customer data to our platform.
If you have any more questions or need further assistance during this process, please feel free to reach out.
```
人家已经写了：“Yes, it typically means that you’ll need to integrate with another payment processor and generate some transaction history before applying for Paddle. ”，但是这条规则就没在 paddle 的官网上明示过。
问题是，如果我已经集成了一个 payment processor ，我干嘛还要再费那个劲迁移到 paddle 啊？ MoR 的服务又不只 paddle 一家。
Select Language