standarts import paths fixed

near-contract-standards/src/non_fungible_token/approval/approval_receiver.ts

@@ -1,5 +1,4 @@
-import { PromiseOrValue } from "near-sdk-js/lib";
-import { AccountId } from "near-sdk-js/lib/types";
+import { AccountId, PromiseOrValue } from "near-sdk-js";
 import { TokenId } from "../token";
 
 /** Approval receiver is the interface for the method called (or attempted to be called) when an NFT contract adds an approval for an account. */

near-contract-standards/src/non_fungible_token/approval/index.ts

@@ -1,5 +1,4 @@
-import { AccountId } from "near-sdk-js/lib/types";
-import { NearPromise } from "near-sdk-js/lib";
+import { AccountId, NearPromise } from "near-sdk-js";
 import { TokenId } from "../token";
 import { Option } from "../utils";
 

near-contract-standards/src/non_fungible_token/core/index.ts

@@ -1,4 +1,4 @@
-import { AccountId } from "near-sdk-js/lib/types";
+import { AccountId } from "near-sdk-js";
 import { Token, TokenId } from "../token";
 import { Option } from "../utils";
 

near-contract-standards/src/non_fungible_token/core/receiver.ts

@@ -1,5 +1,4 @@
-import { PromiseOrValue } from "near-sdk-js/lib";
-import { AccountId } from "near-sdk-js/lib/types";
+import { AccountId, PromiseOrValue } from "near-sdk-js";
 import { TokenId } from "../token";
 
 /** Used when an NFT is transferred using `nft_transfer_call`. This interface is implemented on the receiving contract, not on the NFT contract. */

near-contract-standards/src/non_fungible_token/core/resolver.ts

@@ -1,4 +1,4 @@
-import { AccountId } from "../../../../lib/types";
+import { AccountId } from "near-sdk-js";
 import { TokenId } from "../token";
 import { Option } from "../utils";
 

near-contract-standards/src/non_fungible_token/enumeration/index.ts

@@ -1,4 +1,4 @@
-import { AccountId } from "../../../../lib/types";
+import { AccountId } from "near-sdk-js";
 import { Token } from "../token";
 
 /** Offers methods helpful in determining account ownership of NFTs and provides a way to page through NFTs per owner, determine total supply, etc. */

near-contract-standards/src/non_fungible_token/events.ts

@@ -13,7 +13,7 @@
  * [`NftMint.emit_many`], [`NftTransfer.emit_many`],
  * or [`NftBurn.emit_many`] respectively.
  */
-import { AccountId } from "near-sdk-js/lib/types";
+import { AccountId } from "near-sdk-js";
 import { NearEvent } from "../event";
 import { TokenId } from "./token";
 import { Option } from "./utils";

near-contract-standards/src/non_fungible_token/impl.ts

@@ -1,4 +1,5 @@
 import {
+  AccountId,
   UnorderedMap,
   LookupMap,
   Bytes,
@@ -7,8 +8,8 @@ import {
   assert,
   NearPromise,
   bytes,
-} from "near-sdk-js/lib";
-import { serialize } from "near-sdk-js/lib/utils";
+  serialize,
+} from "near-sdk-js";
 import { TokenMetadata } from "./metadata";
 import {
   refund_approved_account_ids,
@@ -23,7 +24,6 @@ import {
 } from "./utils";
 import { NftMint, NftTransfer } from "./events";
 import { NonFungibleTokenResolver } from "./core/resolver";
-import { AccountId } from "near-sdk-js/lib/types/index";
 import { Token, TokenId } from "./token";
 import { NonFungibleTokenCore } from "./core";
 import { NonFungibleTokenApproval } from "./approval";

near-contract-standards/src/non_fungible_token/metadata.ts

@@ -1,5 +1,4 @@
-import { Bytes } from "near-sdk-js";
-import { assert } from "near-sdk-js";
+import { assert, Bytes } from "near-sdk-js";
 import { Option } from "./utils";
 
 /** This spec can be treated like a version of the standard. */

near-contract-standards/src/non_fungible_token/token.ts

@@ -1,5 +1,5 @@
 import { TokenMetadata } from "./metadata";
-import { AccountId } from "near-sdk-js/lib/types";
+import { AccountId } from "near-sdk-js";
 import { Option } from "./utils";
 
 /** Note that token IDs for NFTs are strings on NEAR. It's still fine to use autoincrementing numbers as unique IDs if desired, but they should be stringified. This is to make IDs more future-proof as chain-agnostic conventions and standards arise, and allows for more flexibility with considerations like bridging NFTs across chains, etc. */

near-contract-standards/src/non_fungible_token/utils.ts

@@ -1,5 +1,4 @@
-import { near, assert, Bytes } from "near-sdk-js";
-import { AccountId } from "near-sdk-js/lib/types";
+import { near, assert, Bytes, AccountId } from "near-sdk-js";
 
 export function bytes_for_approved_account_id(account_id: AccountId): number {
   // The extra 4 bytes are coming from Borsh serialization to store the length of the string.