alexandr-g / cra-template-typescript-redux Goto Github PK

Hi,

I am getting an error after running yarn create react-app your-project-name --template typescript-redux or npx create-react-app your-project-name --template typescript-redux, at the end of the installation shows the error: TypeError: Cannot add property noFallthroughCasesInSwitch, object is not extensible
at verifyTypeScriptSetup (/Volumes/Transcend/Devs/reactjs/your-project-name/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:231:45)
at module.exports (/Volumes/Transcend/Devs/reactjs/your-project-name/node_modules/react-scripts/scripts/init.js:336:5)
at [eval]:3:14
at Script.runInThisContext (vm.js:120:20)
at Object.runInThisContext (vm.js:311:38)
at Object. ([eval]-wrapper:10:26)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at evalScript (internal/process/execution.js:94:25)
at internal/main/eval_string.js:23:3

Hope this info can be helpful to you to fix the issue. Thank you in advance.

Regards,

Thanks for this build!!! Gonna use it to build all my React projects!

Hint: If you could integrate Relay(GraphQL) that would be more than fantastic.

https://github.com/actions/cache

Warning: React does not recognize the computedMatch prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase computedmatch instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in div (at App.tsx:13)
in Switch (at App.tsx:12)
in Router (created by BrowserRouter)
in BrowserRouter (at App.tsx:10)
in App (at src/index.tsx:12)
in Provider (at src/index.tsx:11)

Browser: Google Chrome/Microsoft Edge

According to the documentation: https://reacttraining.com/react-router/web/api/Switch

All children of a <Switch> should be <Route> or <Redirect> elements. Only the first child to match the current location will be rendered.

It looks like you have a div inside the switch statement.

This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• chore(deps): update codecov/codecov-action action to v3
• chore(deps): update github/codeql-action action to v2
• fix(deps): update dependency @types/react to v18
• fix(deps): update dependency @types/react-dom to v18
• fix(deps): update dependency eslint-config-airbnb-typescript to v17
• fix(deps): update dependency react-redux to v8
• fix(deps): update react monorepo to v18 (major) (react, react-dom)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @semantic-release/github to v8.0.4
• fix(deps): update dependency react-scripts to v5.0.1
• chore(deps): update dependency cypress to v9.7.0
• fix(deps): update dependency @typescript-eslint/parser to v5.26.0
• fix(deps): update dependency typescript to ~4.7.0
• chore(deps): update actions/cache action to v3
• chore(deps): update actions/setup-node action to v3
• chore(deps): update cycjimmy/semantic-release-action action to v3
• chore(deps): update dependency semantic-release to v19
• fix(deps): update dependency @types/node to v16
• fix(deps): update dependency react-router-dom to v6
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

I tried the template, and it failed on WSL. See log.

npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "i" "cra-template-typescript-redux"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code EMISSINGARG

npm ERR! typeerror Error: Missing required argument #1
npm ERR! typeerror     at andLogAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
npm ERR! typeerror     at fetchPackageMetadata (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
npm ERR! typeerror     at resolveWithNewModule (/usr/share/npm/lib/install/deps.js:456:12)
npm ERR! typeerror     at /usr/share/npm/lib/install/deps.js:457:7
npm ERR! typeerror     at /usr/share/npm/node_modules/iferr/index.js:13:50
npm ERR! typeerror     at /usr/share/npm/lib/fetch-package-metadata.js:37:12
npm ERR! typeerror     at addRequestedAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
npm ERR! typeerror     at returnAndAddMetadata (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
npm ERR! typeerror     at pickVersionFromRegistryDocument (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
npm ERR! typeerror     at /usr/share/npm/node_modules/iferr/index.js:13:50
npm ERR! typeerror This is an error with npm itself. Please report this error at:
npm ERR! typeerror     <http://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/c/Users/crayf/navico/systembuilder/src/npm-debug.log

It worked on Mac native.
npm-debug.log

The following changes are being made to your tsconfig.json file:

• compilerOptions.jsx must be react-jsx (to support the new JSX transform in React 17)

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Enzyme doesn't support React 17 yet enzymejs/enzyme#2429, need to wait for enzyme-adapter-react-17 to be able to run tests without errors.

enzymejs/enzyme#2462 (comment)