-
-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get error after yarn dev
#214
Comments
yarn dev
cause error: "ReferenceError: Element is not defined"
yarn dev
cause error: "ReferenceError: Element is not defined"yarn dev
Does somebody use this boilerplate? Am I the only won how tried |
Here is the solution: |
I noticed this error too. Seems to happen randomly. Affects |
Waiting for the release of |
How to prevent |
@taime You can fork it and release a fixed version of repo. Then install the |
I published a temporary fix, as such, this package will not be maintained and should only be used for development purposes only. The package is Click here for installation instructions. |
@mattcarlotta Great solution atm 👍 |
@wellyshen How to install react-router-dom from fork? |
@mattcarlotta doesn't work, still got
|
@taime I see the problem. I'll try to fix it later. |
@taime I managed to fix the problem for the time being. Remove the old |
@martin2786 about your idea with aliaces, may be something like this should work
@wellyshen thanks, but it looks like, I can not find in react-router repo place that should be fixed as I wrote above. Here is my fork repo https://github.com/taime/react-router, and I cant find |
Alrighty, round 2! There appears to be a problem with using webpack's Step 1: Run
Step 5: Continue to use |
@mattcarlotta
Have you tried this steps for yourself for clean install react-cool-starte? Does it work? |
By the way, I've found another solution. steps: 1) run
2) edit package.json and change 3) run
|
@taime Your problem is here:
You've added an Anyway, try this forked version. |
As of the latest NPM release (
Side note: it looks like there aren't docs yet for the aliasing function within the install docs, but I was able to deduce the functionality from the corresponding test, found in |
@parties Great find! That works well with one caveat: It shows up as installing
Since this just a temporary fix, I want to make sure it's obvious that |
Fixed in v2.8.5 |
yarn dev
causeReferenceError: Element is not defined
How to repeat
Full error log
system:
mac os
node v11.7.0
yarn v1.13.0
npm v6.5.0
Dependencies
The text was updated successfully, but these errors were encountered: