Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
"webpack-merge": "^5.10.0"
},
"dependencies": {
"@types/node": "^22.7.5",
Copy link
Contributor

Choose a reason for hiding this comment

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

Does it work if this is 18 instead of 22?

I'm confused about the relationship of the copyFiles.ts scripts vs the packages/x/package.json declarations.

As an alternative to fs as any, maybe we could use the techdebt.test.ts reminder to remind us to remove this top-level dependency when the getMinNodejsVersion result is new enough?

Copy link
Contributor Author

@Hweinstock Hweinstock Oct 16, 2024

Choose a reason for hiding this comment

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

Looks like that works as well, I can update the techdebt test to match. I thought avoiding the dependency was more important than the any workaround. But I guess the version bump isn't something to worry about? Are there any other tradeoffs to consider?

Copy link
Contributor

Choose a reason for hiding this comment

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

I thought avoiding the dependency was more important than the any workaround.

Since this PR makes the total cost clearer (i.e.: small :), I'm having doubts. And also, since the risk is covered by techdebt.test.ts in either case, perhaps it's better to have type checking.

Either way is fine IMO.

Copy link
Contributor Author

@Hweinstock Hweinstock Oct 17, 2024

Choose a reason for hiding this comment

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

I think I'll keep the dependency then. Since its just a version bump (to an old stable version) and not a whole new thing, the cost seems very low. The any code doesn't read well, and could cause confusion to someone without the necessary context.

"@types/node": "^18.19.55",
"vscode-nls": "^5.2.0",
"vscode-nls-dev": "^4.0.4"
}
Expand Down
2 changes: 2 additions & 0 deletions packages/core/src/test/techdebt.test.ts
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,8 @@ describe('tech debt', function () {
semver.lt(minNodejs, '18.0.0'),
'with node16+, we can now use AbortController to cancel Node things (child processes, HTTP requests, etc.)'
)
// This is relevant for the use of `fs.cpSync` in the copyFiles scripts.
assert.ok(semver.lt(minNodejs, '18.0.0'), 'with node18+, we can remove the dependency on @types/node@18')
})

it('remove separate sessions login edge cases', async function () {
Expand Down
Loading