-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
[Bug Report] Dev build from source fails #18304
Comments
I suspect that you made some errors during the installation, you can try to reinstall the dependencies. |
Already tried deleting node_modules and reinstalling, same issue, tried with a clean clone, same issue |
You can try to reinstall dependencies using |
Just tried I got a warning during install Don't know if it's related PS: I ruled out a possible global package conflict by uninstalling all my global packages |
Webpack profiling output for one of the errors is:
Command used => The other webpack command runs fine ( Hopefully that helps because I have no clue about what the problem is at this point And being unable to compile from source is quite frustrating because I can't test changes and pull requests |
Can you post the current branch names, .babelrc, node and npm versions? I can restore your situation on my machine, because according to the information you told, I can't analyze the problem. |
Branch is |
Please provide a reproduction repo
| |
Link
|
|
邮箱:[email protected]
|
Signature is customized by Netease Mail Master
On 12/06/2019 21:00, Adrien Foulon wrote:
Branch is dev (It was in the url)
.babelrc is exactly the same
Npm: 6.13.1
Node: v10.15.2
Webpack: 4.41.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Well I said that I'm cloning the original repo on dev, I don't see what a reproduction repo being exactly the same will add I can add the node_modules folder but it's gonna be pretty much the same since it seems being environment related (maybe a path variable story like vue cli) |
Sorry, I responded directly in the mailbox, only to find that the reply was wrong. I will try to recover your problem to help you
| |
Link
|
|
邮箱:[email protected]
|
Signature is customized by Netease Mail Master
On 12/06/2019 22:56, Adrien Foulon wrote:
Well I said that I'm cloning the original repo on dev, I don't see what a reproduction repo being exactly the same will add
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I use the same environment / command as you, but it doesn't happen to you, I don't think this is a problem with |
I finally figured it out... For some reason if the directory is cloned into another node_modules directory (eg: my_project/node_modules/element-ui/) Then the build fails, if not then all works correctly, I'm guessing there is something wrong with how directory are handled on the jsx vue plugin |
Having found the source of the bug and a solution for it I will reopen this until a PR fixes the config Issue is in
Because the regex doesn't care about the tree directory, if the project is under a node modules directory, everything will be excluded Replacing it with |
…ctory named 'node_modules') Instead of a regex for exclusion, this PR resolves the actual path for the excluded files
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Element UI version
2.13.0
OS/Browsers version
Linux (Kubuntu 19)
Vue version
2.6.10
Reproduction Link
https://github.com/ElemeFE/element.git#dev
Steps to reproduce
Simply clone the dev branch
And run
npm install && npm run dist
What is Expected?
The build process to run successfully
What is actually happening?
The build process fails at 89% with a ton of errors like the following
It seems like the jsx loader is not correctly configured
The text was updated successfully, but these errors were encountered: