What is the purpose of the

startDevEnv

script? How is it different from the

startTestingEnv

script?

What is the purpose of the

startDevEnv

script? How is it different from the

startTestingEnv

script?

I also asked here: https://github.com/supertokens/supertokens-root/pull/8

startDevEnv

was an older version of

startTestingEnv

. It's no longer needed and I have removed it.

Is it merged? My copy still has it

haha yea.. i just pushed it to master

I'm going to add a

.testEnvStarted

file to check if the env has been started, so that if you run the file again it doesn't run twice. I also added a check to throw an error if the tests run when that file doesn't exist.

Sounds good! WOuld this file be created if you run it without the

--wait

option too?

Yeah, it's just to see if all of the files/dirs are in the right place for the test env

I think the pre commit hook shouldn't modify the code.

Yeah, okay

no the instrs in the readme are correct

If I run:

java -classpath "./core/*:./plugin-interface/*" io.supertokens.Main ./ DEV

Or:

java -classpath "./supertokens-core/*:./supertokens-plugin-interface/*" io.supertokens.Main ./ DEV

It throws:

Error: Could not find or load main class io.supertokens.Main
Caused by: java.lang.ClassNotFoundException: io.supertokens.Main

Which dir are you running this from?

Root

hmm

I can run the tests fine

> Is it possible to run from a Gradle task? Im don't know how this would work

It doesn't appear that the dependencies are set up correctly in the

build.gradle

files right now

So the plugin is injected into the core dynamically - that's why it's not a dependency to the core project. The dynamic injection causes all the complications

Windows, I'm working on a PR that fixes all of the Windows-specific issues

I see. That's why it's not working

What is the meaning of the colon?

it's a separator

Ah

that load jars from ./core and from ./plugin-interface

Shouldn't that be

supertokens-core

and

supertokens-plugin-interface

?

no. It should points to the build JARs. When you run

./startTesitingEnv --wait

, it moves the JARs of the projects to the

supertokens-root/core

and to

supertokens-root/plugin-interface

. This is done so that we mimic the installation directory structure

So that's the part I didn't get, I didn't realize that the test env had to be running

ah yeaaa.. i see

I might look into refactoring some of that after I finish this Windows PR

that would be super helpful :))

I was actually wondering if you would consider allowing me to join your team? I looked into a few of the positions that you have posted, but I am more into backend-type work rather than frontend React.

We can consider it! Let's get on a call to discuss this? https://calendly.com/supertokens-rishabh/20-mins-intro-call

Thanks!