Instructions on manually creating a project

[spapas]

Hello, I'd like to ask if it would be possible to add some instructions to manually create a new project using reactivated. I am using windows cmd as my Dev env and i can't use nix. I also don't want to use docker.

Even creating a small GitHub project template with a package.json (for js deps) and a requirements.txt (for python deps) containing the sample app that we can clone should be enough.

Please don't force people to use exotic tools just to geverate a simple project to take a peek at how this is working!

Thank you and best regards,
Serafeim

[spapas]

I just found out this page https://www.reactivated.io/documentation/existing-projects/ that covers my request! Can we close this discussion? Thank you!

[silviogutierrez]

Great! Let me know if you have any feedback.

[spapas]

Hello @silviogutierrez I tried creating a new project manually by following the instructions on https://www.reactivated.io/documentation/existing-projects/. The project is here if you wanna take a look: https://github.com/spapas/reactiv (please notice I'm using windows)

Now, I'm trying to try the project and although runserver works, when I visit the homepage I get the following error:

node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'C:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Also, I tried running the build management command (which I don't really understand what it does but I tried it anyway) and got the following error now:

Traceback (most recent call last):
  File "C:\progr\py3\reactiv\reactiv\manage.py", line 22, in <module>
    main()
  File "C:\progr\py3\reactiv\reactiv\manage.py", line 18, in main
    execute_from_command_line(sys.argv)
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\core\management\__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\core\management\__init__.py", line 440, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\core\management\base.py", line 414, in run_from_argv
    self.execute(*args, **cmd_options)
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\core\management\base.py", line 460, in execute
    output = self.handle(*args, **options)
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\reactivated\management\commands\build.py", line 34, in handle
    tsc_process = subprocess.Popen(
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.1520.0_x64__qbz5n2kfra8p0\lib\subprocess.py", line 969, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.1520.0_x64__qbz5n2kfra8p0\lib\subprocess.py", line 1438, in _execute_child
    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
OSError: [WinError 193] %1 is not a valid Win32 application

This error probably is related to the fact that you are trying to run tsc directly on https://github.com/silviogutierrez/reactivated/blob/main/reactivated/management/commands/build.py#L35 and this isn't executable in windows. I guess with some love this can be fixed to start a different script on windows. But can you explain what the build management command does and if it is needed? And also if you have any idea why the home view isn't working?

Thank you!

[silviogutierrez]

Hi again,

You're on the right track: this is because we're trying to run tsc manually. But the other error is a similar issue: we're trying to run node manually to start the renderer.js process.

So both errors would be fixed by having a way to start processes in a system agnostic way. Look at the processes.py file and see if you can hack it into running on windows.

Thereafter, the fix for build.py would be similar. Hope that gives you something to work with.

[spapas]

Hello @silviogutierrez I changed a bit the build.py so as to work better with windows (see my fork here: https://github.com/spapas/reactivated)

Now, when I try to run the build management command it seems to be working with a warning ?

(node:5336) [DEP0128] DeprecationWarning: Invalid 'main' field in 'C:\progr\py3\reactiv\reactiv\node_modules\reactivated\package.json' of 'lib/index.js'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
CommandError: TypeScript error. Run 'tsc --noEmit' manually.

However, when I run the runserver I get the following:

(venv) c:\progr\py3\reactiv\reactiv>python manage.py runserver
[27/Jun/2022 21:51:37,361] Generating interfaces and client side code
[27/Jun/2022 21:51:37,362] Skipping generation as nothing has changed
start_tsc
start_client
start_renderer
start_renderer 2
'node_modules' is not recognized as an internal or external command,
operable program or batch file.
(node:13616) [DEP0128] DeprecationWarning: Invalid 'main' field in 'c:\progr\py3\reactiv\reactiv\node_modules\reactivated\package.json' of 'lib/index.js'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
node:events:368
      throw er; // Unhandled 'error' event
      ^

Error: listen EACCES: permission denied node_modules/_reactivated/reactivated.sock
    at Server.setupListenHandle [as _listen2] (node:net:1317:21)
    at listenInCluster (node:net:1382:12)
    at Server.listen (node:net:1480:5)
    at node_modules/reactivated/renderer.js (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:20840:20)
    at __require (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:12:44)
    at Object.<anonymous> (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:20857:34)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1361:8)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'EACCES',
  errno: -4092,
  syscall: 'listen',
  address: 'node_modules/_reactivated/reactivated.sock',
  port: -1
}

I presume it tries to start a unix socket which isn't working under windows. So I set it to set REACTIVATED_SOCKET=9999 and retry:

[27/Jun/2022 21:52:24,828] Generating interfaces and client side code
[27/Jun/2022 21:52:24,828] Skipping generation as nothing has changed
start_tsc
start_client
start_renderer
'node_modules' is not recognized as an internal or external command,
operable program or batch file.
start_renderer 2
(node:11596) [DEP0128] DeprecationWarning: Invalid 'main' field in 'c:\progr\py3\reactiv\reactiv\node_modules\reactivated\package.json' of 'lib/index.js'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
start_renderer 3
Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
June 27, 2022 - 21:52:26
Django version 4.0.5, using settings 'reactiv.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.

Now the error is (I won't paste the full stacktrace): module 'socket' has no attribute 'AF_UNIX' ; it seems that somebody wants to use a unix socket :|

To try to resolve that, I changed the proper lines of renderer.py to:

session = requests.Session()
response = session.post(f"http://127.0.0.1:{socket}", headers=headers, data=data)

Now I get a completely different error that I don't know how to solve:

Internal Server Error: /
Traceback (most recent call last):
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\core\handlers\exception.py", line 55, in inner
    response = get_response(request)
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\core\handlers\base.py", line 220, in _get_response
    response = response.render()
  File "C:\Users\serafeim\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\django\template\response.py", line 114, in render
    self.content = self.rendered_content
  File "c:\progr\py3\reactiv\reactivated\reactivated\templates.py", line 50, in rendered_content
    return template.render(context, self._request)
  File "c:\progr\py3\reactiv\reactivated\reactivated\backend.py", line 81, in render
    return render_jsx_to_string(request, serialized_context, props)
  File "c:\progr\py3\reactiv\reactivated\reactivated\renderer.py", line 106, in render_jsx_to_string
    raise Exception(response.json()["stack"])
Exception: TypeError: Cannot read properties of undefined (reading '_context')
    at Object.useContext (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:1293:26)
    at Layout (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:20467:45)
    at renderWithHooks (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9673:24)
    at renderIndeterminateComponent (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9730:23)
    at renderElement (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9886:15)
    at renderNodeDestructiveImpl (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9990:17)
    at renderNodeDestructive (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9970:22)
    at renderIndeterminateComponent (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9766:15)
    at renderElement (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9886:15)
    at renderNodeDestructiveImpl (c:\progr\py3\reactiv\reactiv\node_modules\_reactivated\renderer.js:9990:17)

Do you have any idea? Maybe I've done some bad configuration with my project. Can you take a peek? https://github.com/spapas/reactiv

TIA!

[silviogutierrez]

Hi there, see #187 for some background here. First build assets manually with:

python manage.py generate_client_assets

Then in two separate tabs (using whatever Windows syntax you need):

SOCKET_PATH=9999 node node_modules/reactivated/build.renderer.js

REACTIVATED_RENDERER=http://127.0.0.1:9999 python manage.py runserver

And then hack renderer.py as you did to avoid forcing a unix socket. That could work.

[spapas]

Hello @silviogutierrez thank you for the help. I followed your steps however when I tried to run build.renderer.js I get the following error:

(venv) C:\progr\py3\reactiv\reactiv>node node_modules\reactivated\build.renderer.js
 > node_modules/reactivated/renderer.js:37:21: error: Could not resolve "../../node_modules/_reactivated"
    37 │     var _b = require("../../node_modules/_reactivated"), Provider = _b.Provider, getTemplate = _b.getTemplate;
       ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I have node js v 16:

(venv) C:\progr\py3\reactiv\reactiv>node -v
v16.15.1

and I've run npm install on my project folder:

(venv) C:\progr\py3\reactiv\reactiv>npm install
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

up to date, audited 551 packages in 1s

83 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Any idea? TIA

[spapas]

No, unfortunately I still can't make it run. I don't think it's the correct way to debug it like this. I'm giving up, sorry. Thank you for trying.

[silviogutierrez]

Understood. If you feel like it, give the Docker version a try, that may work better on Windows.

[spapas]

Good idea! I'll try the docker version instead! Thank you

[spapas]

Hey @silviogutierrez finally, I was able to make it work using docker + wsl :)

It's very impressive !

[silviogutierrez]

Great news. Thanks for letting me know it worked.