-
Notifications
You must be signed in to change notification settings - Fork 55
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
Upgrade to slang 0.19 and use prettier 3 on the codebase #635
Open
antico5
wants to merge
4
commits into
development
Choose a base branch
from
upgrade-slang-0.19
base: development
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We only updated the output previously.
This was previously implicit and depended on a the root build. This clashes with my attempts to update the typescript version, so I am scoping the e2e tests to their own build.
This commit at its heart does the following: 1. Updates the version of typescript we are using to 5.5 2. Switches to node16 as our module resolution strategy 3. Updates the underlying node-language-server version we are using These are all initial steps to allow us to pull in ESM module based dependencies, in particular `slang@19`. * chore: add eslint config for coc This brings coc inline with the eslint config pattern found for other packages in the repo. It showed up as an issue when attempting to update the typescript version. * chore: bump version of language server The language server was 2 years out of date. To maximize ease of integration with typescript@5 we are updating to the latest version. * chore: bump version of lodash types The latest version of lodash types is been taken to better work with typescript@5. * chore: bump version of eslint and plugins Eslint and its plugins are 2 years out of date. They have been brought up to the same version used in the Hardhat repo. We initially tried to jump straight to `eslint@10` but backed out with the config format changes. We will look at this again with the repo modernization efforts. * chore: bump verion of @types/node to latest Node 20 is now the version used in VSCode. The types have been updated to reflect the new node versions. * chore: bump version of esbuild To package the extension we use a bundler, esbuild needs to be updated to match the new version of typescript. * chore: update version of typescript We need better module resolution support as we deal with Slang's ESM packages, specifically the loading of TS types from commonjs. * chore: bump node target in tsconfig To support pulling in more modern ts libraries like Slang@18, we want to swap to `node16` module resolution. This is not ESM, but the modern version of commonjs. It lets us use TS types from Slang from the VSCode extension's commonjs packages. * chore: disable lib check on server This is a hack that we should accept temporarily. A library that the language server node library uses fails more refined typechecking in typescript@5. For the moment checking types in dependent packages is skipped. * chore: fix linting error on t.type The update to eslint revealed this equality error. * chore: update eslint errors New rules are affecting our naming conventions. Rather than disable the rule I have scattered disable lines. This is a tradeoff, but we expect a revamp of the eslint rules based on HH3 in the near future. * Update bundle script - @solidity-parser got hoisted --------- Co-authored-by: Armando Andini <[email protected]>
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #632