You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: apps/nextra/pages/en/build/smart-contracts/book/packages.mdx
+25
Original file line number
Diff line number
Diff line change
@@ -409,3 +409,28 @@ Foo = { local = "../C" }
409
409
```
410
410
411
411
Note that if both the bytecode and the source code of the same package exist in the search paths, the compiler will complain that the declaration is duplicated.
412
+
413
+
## Overriding the Standard Libraries
414
+
When working with third-party packages, you might encounter issues where different versions of the Move and Aptos standard library packages are referenced.
415
+
416
+
This can lead to package resolution failures.
417
+
418
+
```
419
+
"Error": "Move compilation failed:
420
+
Unable to resolve packages for package 'C':
421
+
While resolving dependency 'B' in package 'C':
422
+
Unable to resolve package dependency 'B':
423
+
While resolving dependency 'AptosFramework' in package 'B':
424
+
Unable to resolve package dependency 'AptosFramework':
425
+
Conflicting dependencies found: package 'AptosFramework' conflicts with 'AptosFramework'
426
+
```
427
+
To resolve this, you can override the standard library packages using a command-line option. This allows you to enforce a specific version of the standard libraries across your entire dependency tree.
428
+
429
+
You can apply the override to commands like `aptos move compile`, `aptos move run`, and others. Here is the syntax:
0 commit comments