Support For React18, Updated Dependencies #24
Conversation
…mplemented jsdom methods
|
The previous commits from when this PR was opened did not actually work with TypeScript. This issue stems from webpack. Just compiling the project with |
|
@robert-harbison has there been any updates on this pull request? |
|
@robert-harbison have you had a chance to look at this yet? People are starting to suggest name-squatting packages in order to fulfill what this PR attempts to accomplish. |
|
@robert-harbison please take a look at this and update it. |
|
@robert-harbison any plans to merge this ? I have just tried this out by building local and it works :) nice work @jaxtonw. |
|
Someone should make a good fork and maintain it :/ |
|
Hi @jaxtonw, I made a new repo (with react18 support) for the same purpose on https://github.com/PabloLION/xterm-react and I'm trying to improve it. I like the tests you've written. Would you mind to make a similar PR in my repo, or if I copy them from this PR directly? P.S. I have an end-to-end test with vite, and I'm planning to host it with GitHub Pages as a live example. You might want to consider how to integrate the test with that as well |
Updated the project and all it's dependencies to build again and support React 18. Previous packages were deprecated and the project in it's current state did not build. This has since been fixed, and with updated dependencies, it should hopefully last for a while.
The version has been updated to 1.1.0. I debated versioning to 2.0.0, but this shouldn't cause any major breaking changes for React 16/17 to my knowledge.
I apologize if any of the configuration changes when updating dependencies conflict with the initial plans of the project. I struggled a bit in trying to keep things as similar as similar as possible while not being able to build the old version.
Any critiques or suggestions are appreciated!