Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to npm workspaces #340

Merged
merged 9 commits into from
Apr 8, 2022
Merged

Switch to npm workspaces #340

merged 9 commits into from
Apr 8, 2022

Conversation

kaisalmen
Copy link
Collaborator

@kaisalmen kaisalmen commented Apr 6, 2022

This implements #331 and substantially changes the repositories structure, build process and tooling. It does not change code apart from compiler error fixes required after TypeScript update:

  • Switch to npm workspace and vite and thereby drop yarn, lerna and webpack
  • Restructure project: All code is moved to packages directory
  • Update and clean-up all dependencies
  • Use monaco-editor in examples instead of monaco-editor-core Does it make sense to switch to monaco-editor instead of monaco-editor-core #337
  • README is fully updated
  • Introduce GitHub Actions
  • Reconnecting websocket has been removed from the example

This PR could be best checked with a fresh checkout. Please have a look at the updated README if the instructions are good and sufficient. Please check if the example still work as expected. I think so, but I am only involved here since a couple of weeks and may have missed something or misunderstood something.

- client keeps original typescript config for now
- Test vite in examples/client
- Moved vite to top level
- Removed substantial amount of devDependencies due to webpack removal
- Fixed compile issues (browser example)
- Fixed error regression in vscode-compatibility
- Cleaned-up all tsconfig.json
- Fix gitpod config
- Update Copyright statements
- Fix vscode launch configs
- Remove unneeded files
@kaisalmen
Copy link
Collaborator Author

I removed the travis-ci check now. With this PR we get GitHub Actions that we can extend over time if we see the need.

package.json Outdated Show resolved Hide resolved
packages/client/src/vscode-compatibility.ts Outdated Show resolved Hide resolved
packages/example-browser/src/main.ts Outdated Show resolved Hide resolved
packages/example-browser/webpack.config.js Outdated Show resolved Hide resolved
packages/example-client/src/json-server.ts Outdated Show resolved Hide resolved
packages/example-client/src/json-server.ts Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@CGNonofr
Copy link
Collaborator

CGNonofr commented Apr 6, 2022

There is a lot of changes so it's hard to review, there is also some comments that are not relevant anymore I think

@kaisalmen
Copy link
Collaborator Author

There is a lot of changes so it's hard to review, there is also some comments that are not relevant anymore I think

My apologies. This is maily about built, tools and dependencies and not about what the code really does.
What about: Let's not do any code changes apart from needed-because-of-newer-compiler-version in this PR, but open another PR (there are at least two things you recognized, I guess there are more).

Did you have time to try it out, btw?

@kaisalmen
Copy link
Collaborator Author

I added these two points to #315:

  • Introduce semantic release
  • Improve code where easily possible

Copy link
Collaborator

@CGNonofr CGNonofr left a comment

Choose a reason for hiding this comment

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

LGTM

@kaisalmen kaisalmen mentioned this pull request Apr 8, 2022
5 tasks
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.

None yet

2 participants