blsmedia/sign
2
0
Fork 0
Code Issues Packages Releases Activity
Files
0cfe256412b756481c45296533cb3f657b2bf802
sign/apps/marketing/package.json

60 lines
1.7 KiB
JSON
Raw Normal View History

wip: refresh design
2023-06-09 18:21:18 +10:00
{
"name": "@documenso/marketing",
v1.8.1-rc.0
2024-11-20 23:02:32 +11:00
"version": "1.8.1-rc.0",
wip: refresh design
2023-06-09 18:21:18 +10:00
"private": true,
"license": "AGPL-3.0",
"scripts": {
fix: use -p cli option for next dev
2023-08-23 17:56:12 -05:00
"dev": "next dev -p 3001",
fix: translate extract command (#1394) Change how the translate extract command is run on build
2024-10-28 11:21:49 +09:00
"build": "npm run translate:extract --prefix ../../ && turbo run translate:compile && next build",
chore: upgrade to next 14.0.0
2023-10-27 15:14:04 +11:00
"start": "next start -p 3001",
refactor: extract common components into UI package
2023-08-23 11:22:13 +10:00
"lint": "next lint",
chore: add some eslint rules (#344)
2023-11-14 14:31:45 +05:30
"lint:fix": "next lint --fix",
fix: support optimise imports
2023-09-21 21:34:24 +10:00
"clean": "rimraf .next && rimraf node_modules",
feat: initial i18n marketing implementation (#1223) ## Description This PR introduces an initial i18n implementation using [Lingui](https://lingui.dev). We plan to combine it with Crowdin which will provide AI translations when PRs are merged into main. We plan to rollout i18n to only marketing for now, and will review how everything goes before continuing to introduce it into the main application. ## Reasoning Why not use i18n-next or other alternatives? To hopefully provide the best DX we chose Lingui because it allows us to simply wrap text that we want to translate in tags, instead of forcing users to do things such as: - Update the text to `t('some-text')` - Extract it to the file - The text becomes a bit unreadable unless done correctly Yes, plugins such as i18n-ally and Sherlock exist to simplify these chores, but these require the user to be correctly setup in vscode, and it also does not seem to provide the required configurations for our multi app and multi UI package setup. ## Super simple demo ```html // Before <p>Text to update</p> // After <p> <Trans>Text to update</Trans> </p> ``` ## Related Issue Relates to #885 but is only for marketing for now. Another branch is slowly being prepared for the changes required for the web application while we wait to see how this goes for marketing. ## Changes Made Our configuration does not follow the general standard since we have translations that cross: - Web app - Marketing app - Constants package - UI package This means we want to separate translations into: 1. Marketing - Only translations extracted from `apps/marketing` 2. Web - Only translations extracted from `apps/web` 3. Common - Translations from `packages/constants` and `packages/ui` Then we bundle, compile and minify the translations for production as follows: 1. Marketing = Marketing + Common 2. Web = Web + Common This allows us to only load the required translations when running each application. Overall general changes: - Add i18n to marketing - Add core i18n setup to web - Add pre-commit hook and GH action to extract any new <Trans> tags into the translation files <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added Romanian localization for marketing messages to improve accessibility for Romanian-speaking users. - Introduced German and English translation modules and PO files to enhance the application's internationalization capabilities. - Integrated internationalization support in the RootLayout component for dynamic language settings based on server-side configurations. - Enhanced the Enterprise component with translation support to adapt to user language preferences. - Added a `<meta>` tag to prevent Google from translating the page content, supporting internationalization efforts. - **Bug Fixes** - Resolved minor issues related to the structure and accessibility of translation files. - **Chores** - Updated project dependencies to support the new localization features and ensure stability. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Lucas Smith <me@lucasjamessmith.me> Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: github-actions <github-actions@documenso.com>
2024-07-26 14:56:42 +10:00
"copy:pdfjs": "node ../../scripts/copy-pdfjs.cjs",
"translate:compile": "lingui compile --typescript"
wip: refresh design
2023-06-09 18:21:18 +10:00
},
"dependencies": {
fix: docker build requires smtp host (#672) set a default for smtp host and add an action for testing docker builds on each pull request
2023-11-22 16:26:39 +11:00
"@documenso/assets": "*",
wip: refresh design
2023-06-09 18:21:18 +10:00
"@documenso/lib": "*",
"@documenso/tailwind-config": "*",
"@documenso/trpc": "*",
"@documenso/ui": "*",
"@hookform/resolvers": "^3.1.0",
chore: upgrade next (#1300)
2024-09-03 09:48:54 +10:00
"@lingui/macro": "^4.11.3",
"@lingui/react": "^4.11.3",
chore: add status widget
2024-03-29 10:10:35 +00:00
"@openstatus/react": "^0.0.3",
feat: initial i18n marketing implementation (#1223) ## Description This PR introduces an initial i18n implementation using [Lingui](https://lingui.dev). We plan to combine it with Crowdin which will provide AI translations when PRs are merged into main. We plan to rollout i18n to only marketing for now, and will review how everything goes before continuing to introduce it into the main application. ## Reasoning Why not use i18n-next or other alternatives? To hopefully provide the best DX we chose Lingui because it allows us to simply wrap text that we want to translate in tags, instead of forcing users to do things such as: - Update the text to `t('some-text')` - Extract it to the file - The text becomes a bit unreadable unless done correctly Yes, plugins such as i18n-ally and Sherlock exist to simplify these chores, but these require the user to be correctly setup in vscode, and it also does not seem to provide the required configurations for our multi app and multi UI package setup. ## Super simple demo ```html // Before <p>Text to update</p> // After <p> <Trans>Text to update</Trans> </p> ``` ## Related Issue Relates to #885 but is only for marketing for now. Another branch is slowly being prepared for the changes required for the web application while we wait to see how this goes for marketing. ## Changes Made Our configuration does not follow the general standard since we have translations that cross: - Web app - Marketing app - Constants package - UI package This means we want to separate translations into: 1. Marketing - Only translations extracted from `apps/marketing` 2. Web - Only translations extracted from `apps/web` 3. Common - Translations from `packages/constants` and `packages/ui` Then we bundle, compile and minify the translations for production as follows: 1. Marketing = Marketing + Common 2. Web = Web + Common This allows us to only load the required translations when running each application. Overall general changes: - Add i18n to marketing - Add core i18n setup to web - Add pre-commit hook and GH action to extract any new <Trans> tags into the translation files <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added Romanian localization for marketing messages to improve accessibility for Romanian-speaking users. - Introduced German and English translation modules and PO files to enhance the application's internationalization capabilities. - Integrated internationalization support in the RootLayout component for dynamic language settings based on server-side configurations. - Enhanced the Enterprise component with translation support to adapt to user language preferences. - Added a `<meta>` tag to prevent Google from translating the page content, supporting internationalization efforts. - **Bug Fixes** - Resolved minor issues related to the structure and accessibility of translation files. - **Chores** - Updated project dependencies to support the new localization features and ensure stability. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Lucas Smith <me@lucasjamessmith.me> Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: github-actions <github-actions@documenso.com>
2024-07-26 14:56:42 +10:00
"cmdk": "^0.2.1",
feat: add content layer Add blog pages Add privacy page
2023-07-27 18:29:22 +10:00
"contentlayer": "^0.3.4",
feat: replace signup widget with carousel
2024-05-23 10:09:36 +00:00
"embla-carousel": "^8.1.3",
"embla-carousel-autoplay": "^8.1.3",
"embla-carousel-react": "^8.1.3",
wip: refresh design
2023-06-09 18:21:18 +10:00
"framer-motion": "^10.12.8",
feat: show monthly new users
2023-11-05 12:48:05 +11:00
"lucide-react": "^0.279.0",
"luxon": "^3.4.0",
wip: refresh design
2023-06-09 18:21:18 +10:00
"micro": "^10.0.1",
chore: upgrade next (#1300)
2024-09-03 09:48:54 +10:00
"next": "14.2.6",
fix: remove server actions (#684)
2023-12-02 09:38:24 +11:00
"next-auth": "4.24.5",
feat: allow editing pending documents (#1346) ## Description Adds the ability for the document owner to edit recipients and their fields after the document has been sent. A recipient can only be updated or deleted if: - The recipient has not inserted any fields - Has not completed the document <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes - **New Features** - Added new localization messages to clarify user actions regarding document signing. - Enhanced French translations for improved user interaction. - **Improvements** - Updated localization strings in German and English for clearer feedback on signer and recipient statuses. - Improved overall structure of localization files for better maintainability. - **Dependency Updates** - Upgraded `next-axiom` and `remeda` libraries to their latest versions, potentially enhancing performance and stability. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Mythie <me@lucasjamessmith.me>
2024-09-20 13:58:21 +10:00
"next-axiom": "^1.5.1",
feat: add content layer Add blog pages Add privacy page
2023-07-27 18:29:22 +10:00
"next-contentlayer": "^0.3.4",
chore: upgrade deps and linting
2023-08-01 17:34:17 +10:00
"next-plausible": "^3.10.1",
wip: refresh design
2023-06-09 18:21:18 +10:00
"perfect-freehand": "^1.2.0",
feat: add single player mode
2023-09-20 13:48:30 +10:00
"posthog-js": "^1.77.3",
chore: upgrade next (#1300)
2024-09-03 09:48:54 +10:00
"react": "^18",
feat: add single player mode
2023-09-20 13:48:30 +10:00
"react-confetti": "^6.1.0",
chore: upgrade next (#1300)
2024-09-03 09:48:54 +10:00
"react-dom": "^18",
wip: refresh design
2023-06-09 18:21:18 +10:00
"react-hook-form": "^7.43.9",
fix: update icons (#468) * fix: update icons
2023-10-04 07:57:36 +05:30
"react-icons": "^4.11.0",
feat: open page
2023-08-01 17:43:11 +10:00
"recharts": "^2.7.2",
chore: downgrade sharp
2024-06-28 12:12:15 +10:00
"sharp": "0.32.6",
chore: upgrade to latest next.js version (#553) * chore: upgrade next.js * fix: canvas not found error * chore: upgrade package for marketing * feat: add isServer conditional * fix: inverse isServer condition * fix: normalize packages * fix: upgrade ee package * fix: depdency nightmares * fix: failing seed script
2023-10-18 17:03:02 +05:30
"typescript": "5.2.2",
chore: update zod to 3.22.4 (#563) * chore: updated zod Signed-off-by: Adithya Krishna <aadithya794@gmail.com> --------- Signed-off-by: Adithya Krishna <aadithya794@gmail.com>
2023-10-19 15:54:05 +05:30
"zod": "^3.22.4"
wip: refresh design
2023-06-09 18:21:18 +10:00
},
"devDependencies": {
chore: upgrade next (#1300)
2024-09-03 09:48:54 +10:00
"@lingui/loader": "^4.11.3",
"@lingui/swc-plugin": "4.0.8",
wip: refresh design
2023-06-09 18:21:18 +10:00
"@types/node": "20.1.0",
chore: upgrade next (#1300)
2024-09-03 09:48:54 +10:00
"@types/react": "^18",
"@types/react-dom": "^18"
wip: refresh design
2023-06-09 18:21:18 +10:00
}
v1.7.2-rc.0
2024-10-08 21:56:44 +11:00
}
Reference in New Issue Copy Permalink