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
{{ message }}
This repository has been archived by the owner on Nov 5, 2022. It is now read-only.
django.template.exceptions.TemplateSyntaxError: Error: Secure random number generation is not supported by this browser.
Use Chrome, Firefox or Internet Explorer 11
I use Firefox 84. So Secure random number generation should be no problem here. Seems to be a ug in one of the old dependencies.
Is there an update in sight? Any chance to support Parcel2, or Vue3?
This would be such a great project...
Thanks.
The text was updated successfully, but these errors were encountered:
The lib isn't actively maintained because I haven't used Parcel in my projects in a while. It seems that both Parcel and Django APIs have had some breaking changes in the meantime. I'll take a look when I get the chance.
The error you're getting is not browser related, but rather NodeJS related because Parcel has to produce two bundles in order for SSR to work: one for the server, the other for browsers. Hence the two separate entry points:server.js and client.js.
For the next update I'll aim to expose most of Parcel config in Django settings, because the idea of the project is to be as thin layer as possible for Django-Parcel integration, and just provide automatic NodeJS render server management.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just wanted to know if this project is still maintained. The default (React) version does not run, when calling
./manage.py runserver
, it outputsAnd the Vuejs version errors:
I use Firefox 84. So Secure random number generation should be no problem here. Seems to be a ug in one of the old dependencies.
Is there an update in sight? Any chance to support Parcel2, or Vue3?
This would be such a great project...
Thanks.
The text was updated successfully, but these errors were encountered: