-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Change typescript module
to nodenext
#32757
Conversation
Typscript will be adding more suitable node targets like |
module
to nodenext
Is |
As per TS docs,
In typescript 5.8 we can switch it to It is urgent in the sense that if we want |
* origin/main: Fix internal server error when updating labels without write permission (go-gitea#32776) Fix wiki ui (go-gitea#32781) Change typescript `module` to `nodenext` (go-gitea#32757) Refactor issue filter (labels, poster, assignee) (go-gitea#32771) Make RepoActionView.vue support `##[group]` (go-gitea#32770) [skip ci] Updated translations via Crowdin
* giteaofficial/main: [skip ci] Updated translations via Crowdin Use batch database operations instead of one by one to optimze api pulls (go-gitea#32680) Fix internal server error when updating labels without write permission (go-gitea#32776) Fix wiki ui (go-gitea#32781) Change typescript `module` to `nodenext` (go-gitea#32757) Refactor issue filter (labels, poster, assignee) (go-gitea#32771)
Typescript 5.7 changed semantics around JSON imports and
nodenext
is now treated differently thannode16
for JSON imports and it requires the import attribute, so change the value to that and add the attribute to eliminate this typescript error.moduleResolution
is treated as an alias whenmodule
isnodenext
, so we don't need to specify it.Also see microsoft/TypeScript#60589. It appears the next Typescript release will fix this for
node16
, but I guess it'll still be good to switch tonodenext
.