c4dc081e70
This ensures we expose the `styled-jsx` types correctly even when the package is not hoisted from next's `node_modules` e.g. when using `pnpm`. We had an existing test that covered this although it installed `styled-jsx` at the top-level as a workaround so the test has been updated to remove this workaround. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/pull/37828#discussion_r901164193
27 lines
738 B
JSON
27 lines
738 B
JSON
{
|
|
"private": true,
|
|
"scripts": {
|
|
"predev": "npm run i18n:compile",
|
|
"dev": "next dev",
|
|
"prebuild": "npm run i18n:compile",
|
|
"build": "next build",
|
|
"start": "next start",
|
|
"lint": "next lint",
|
|
"i18n:extract": "formatjs extract 'pages/**/*.ts*' 'components/**/*.ts*' --out-file lang/en.json",
|
|
"i18n:compile": "formatjs compile-folder lang compiled-lang"
|
|
},
|
|
"dependencies": {
|
|
"next": "11.1.0",
|
|
"react": "17.0.2",
|
|
"react-dom": "17.0.2",
|
|
"react-intl": "5.20.9"
|
|
},
|
|
"devDependencies": {
|
|
"@formatjs/cli": "4.2.31",
|
|
"@types/node": "16.6.2",
|
|
"@types/react": "17.0.19",
|
|
"babel-plugin-formatjs": "10.3.5",
|
|
"eslint-plugin-formatjs": "2.17.4",
|
|
"typescript": "4.3.5"
|
|
}
|
|
}
|