Skip to content

Conversation

Joshuafrankle
Copy link

No description provided.

Copy link
Owner

@blakesanie blakesanie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What was the breaking behavior you encountered in react 18, and what part of the codebase was responsible? Perhaps I am simply unaware but have you found the specific reason? Thanks for the PR :)

"eject": "node ../node_modules/react-scripts/bin/react-scripts.js eject",
"predeploy": "npm run build",
"deploy": "gh-pages -d build"
"start": "parcel index.html",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I checked out this PR, running 'npm run start' under the example directory gives this error in the browser.
Screen Shot 2022-06-18 at 1 57 35 PM

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I checked out this PR, running 'npm run start' under the example directory gives this error in the browser. Screen Shot 2022-06-18 at 1 57 35 PM

I think the example just came with a template, It was not updated

"test:watch": "react-scripts test --env=jsdom",
"predeploy": "cd example && npm install && npm run build",
"deploy": "gh-pages -d example/build"
"start": "tsdx watch",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why, but checking out this PR and installing dependencies with 'npm install --save', then 'npm run start' results in MODULE_NOT_FOUND
Screen Shot 2022-06-18 at 2 01 57 PM

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why, but checking out this PR and installing dependencies with 'npm install --save', then 'npm run start' results in MODULE_NOT_FOUND Screen Shot 2022-06-18 at 2 01 57 PM

Not sure why, it is working fine for me
image

@Joshuafrankle
Copy link
Author

What was the breaking behaviour you encountered in react 18, and what part of the codebase was responsible? Perhaps I am simply unaware but have you found the specific reason? Thanks for the PR :)

I didn't encounter any breaking changes; it was incompatible with the most recent version, which can be fixed with —legacy-peer-deps, but I just want to make it compatible with the most recent react and typescript projects. I'm still not sure if it's perfect because I'm still learning everything.

Copy link

@maxmdev maxmdev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@meri-maki
Copy link

would love to see this pr merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants