Avoid importing from '..' #2187
Merged
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
Import commands from their originating module, not from a re-export module. This is important for compatibility with import-in-the-middle and other import-altering code, otherwise this results in a partially-loaded module being passed into instrumentation code.
roggervalf
reviewed
Sep 20, 2023
src/classes/child.ts
Outdated
| @@ -1,7 +1,7 @@ | |||
| import { ChildProcess, fork } from 'child_process'; | |||
| import { Worker } from 'worker_threads'; | |||
| import { AddressInfo, createServer } from 'net'; | |||
| import { ChildCommand, ParentCommand } from '../'; | |||
| import { ChildCommand, ParentCommand } from '../commands'; | |||
There was a problem hiding this comment.
In commands are our lua scripts
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.
Import commands from their originating module, not from a re-export module.
This is important for compatibility with import-in-the-middle and other import-altering code, otherwise this results in a partially-loaded module being passed into instrumentation code.