feat: first test suite

[andrewgremlich]

Integrating Vitest first test suite.

#17

[netlify]

✅ Deploy Preview for threejs-offset ready!

Name	Link
🔨 Latest commit	c6ccf7c
🔍 Latest deploy log	https://app.netlify.com/projects/threejs-offset/deploys/69055a85c90f7a0008ba169d
😎 Deploy Preview	https://deploy-preview-22--threejs-offset.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[andrewgremlich]

I've got a few things to check

[andrewgremlich]

@AngyDev this PR is ready to go

[AngyDev]

@andrewgremlich thank you, I'll review it in the weekend. Sorry at the moment I don't have the possibility to access to the code.

[AngyDev]

Hi @andrewgremlich,

when I try to run the test or the server, I'm getting this warning

▲ [WARNING] The condition "types" here will never be used as it comes after both "import" and "require" [package.json]

    package.json:15:6:
      15 │       "types": "./lib/index.d.ts"
         ╵       ~~~~~~~

  The "import" condition comes earlier and will be used for all "import" statements:

    package.json:13:6:
      13 │       "import": "./lib/index.es.js",
         ╵       ~~~~~~~~

  The "require" condition comes earlier and will be used for all "require" calls:

    package.json:14:6:
      14 │       "require": "./lib/index.umd.js",

Do you have the same? If yes, could you fix it?

[andrewgremlich]

Howdy @AngyDev ! Yup I'll take a look

[andrewgremlich]

@AngyDev

Huh, for some reason the order matters in this section in package.json.

  "exports": {
    ".": {
      "import": "./lib/index.es.js",
      "require": "./lib/index.umd.js",
      "types": "./lib/index.d.ts"
    }
  },

Also, I realized that those exports don't point to the dist folder. Would you like that?

As well, I changed the nvmrc to point to the most recent node version (24).

[AngyDev]

Yeah, the exports are only for the library. At this point, do we want to use version 25?

[andrewgremlich]

We could use v25! I am initially against using it since it's not a designated LTS version. But since this isn't really an enterprise library, I guess it really doesn't matter. Thoughts?

[AngyDev]

I was thinking the same. In this case, I don't think it is a big deal. Let's see what can happen 😅

[andrewgremlich]

I was thinking the same. In this case, I don't think it is a big deal. Let's see what can happen 😅

As in let's go ahead with v25? I'm good with that

[andrewgremlich]

@AngyDev this is ready to go I think

[AngyDev]

@andrewgremlich Thanks for the updates! The new stuff looks good. Before we merge, can you revisit the older comments regarding the interfaces?

[andrewgremlich]

@andrewgremlich Thanks for the updates! The new stuff looks good. Before we merge, can you revisit the older comments regarding the interfaces?

I'm so sorry... I don't see a comment about interfaces...

[AngyDev]

I'm so sorry, apparently I added the comments to the PR but never saved 😅

[AngyDev]

Thanks, @andrewgremlich, for the contribution 😊