No such module PackagePlugin #1704
Labels
bug
Something isn't working
Comments
|
This was originally reported in swiftlang/vscode-swift#1044 by @samdeane |
|
Synced to Apple’s issue tracker as rdar://136423767 |
ahoppen
added a commit
to ahoppen/sourcekit-lsp
that referenced
this issue
Nov 22, 2024
Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Fixes swiftlang#1704 rdar://136423767
ahoppen
added a commit
to ahoppen/swift-package-manager
that referenced
this issue
Nov 22, 2024
Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Fixes swiftlang/sourcekit-lsp#1704 rdar://136423767
ahoppen
added a commit
to ahoppen/sourcekit-lsp
that referenced
this issue
Nov 22, 2024
Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Fixes swiftlang#1704 rdar://136423767
|
The lack of autocompletion is quite frustrating. Are there any updates on this issue? |
|
Yes, #1846 should fix the issue. |
ahoppen
added a commit
to swiftlang/swift-package-manager
that referenced
this issue
Dec 9, 2024
Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Fixes swiftlang/sourcekit-lsp#1704 rdar://136423767
ahoppen
added a commit
to ahoppen/sourcekit-lsp
that referenced
this issue
Dec 9, 2024
Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Currently, when there‘s a syntax error in a package manifest, we don’t get any build settings from it in SourceKit-LSP and thus loose almost all semantic functionality. If we can’t parse the package manifest, fall back to providing build settings by assuming it has the current Swift tools version. Fixes swiftlang#1704 rdar://136423767
|
This still seems to be an issue? (Tested with swift-DEVELOPMENT-SNAPSHOT-2025-03-25) |
|
That’s probably a different root cause. Could you file a new issue for it and attach the output of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Swift version
swift-driver version: 1.113 Apple Swift version 6.0 (swiftlang-6.0.0.7.6 clang-1600.0.24.1)
Platform
macOS 14
Editor
Visual Studio Code
Does the issue reproduce with Swift 6?
Yes
Description
SourceKit-LSP gives an error diagnostic
No such module PackagePluginwhen trying toimport PackagePluginfor a SwiftPM plugin. This module should be available and give code completion, go to definition, etc.Steps to Reproduce
Clone
[email protected]:elegantchaos/Versionator.gitcheckout 187bc4c0e15dadccb5a65b2f71fa0082bd583f81
open in VSCode and try to edit
Plugins/VersionatorPlugin/plugin.swiftLogging
No response
The text was updated successfully, but these errors were encountered: