-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
"core-js/modules/es.object.set-prototype-of.js". This file can not be found, please check it for typos or update it if the file got moved. #47
Comments
Hi, you need to install |
Installing You should get both of these things automatically with the WebpackEncoreBundle recipe. It seems like some people are getting the webpack.config.js code (part B) but not part A.... but I don't know how. |
I was having this issue (as well as a bunch of other issues installing webpack encore in a Symfony app recently updated to 4.4). I was following the instructions here: https://symfony.com/doc/current/frontend/encore/installation.html |
I am having this issue on a Sf 6.1 with Webpack Encore, even after I installed core-js. |
@Cartman34 I've tried to offer some help about the package over on symfony/webpack-encore#1129 - my guess is that the error is related to working on a package. Specifically, you may not be "building" a dist version of your JS files in your bundle, and then because they live in |
@weaverryan You are totally right, I am a JS developer but not a Node one :D I don't even know I was using babel, webpack uses it implicitly ? How do you to develop locally a JS package ? |
Same error here. I've installed it a dozen times with no issue... but this time {
"devDependencies": {
"bootstrap": "^5.2.1"
}
} ;) wanting to get hands on the frontend too early this time? So, just copy the contents from package.json and run npm install again... hope it helps! |
I am having this errors, not sure how to fix this:
I only have the file:
assets/controllers/hello_controller.js
I have to comment all the export default for solve the encore problems.
The text was updated successfully, but these errors were encountered: