Replies: 5 comments 8 replies
-
|
axios and lodash is no longer available globally, for axios you can swap it with |
Beta Was this translation helpful? Give feedback.
-
|
But I am not using those dependencies myself as said and you can see from the stack trace I have this error with a default scaffolded field with no changes |
Beta Was this translation helpful? Give feedback.
-
|
The default scaffolding should already include
|
Beta Was this translation helpful? Give feedback.
-
|
It does yes. I can see it also in the package.json generated but the error that i am getting is from the vendor files |
Beta Was this translation helpful? Give feedback.
-
|
Yes I have the same problem |
Beta Was this translation helpful? Give feedback.
-
|
I think it has to do with laravel mix. Whenever I run |
Beta Was this translation helpful? Give feedback.
-
|
I solved the problem.
All errors gone. |
Beta Was this translation helpful? Give feedback.
-
|
@crynobone Wait now how is this a valid solution? Manipulating the vendor files doesn't sound like something that should be required. |
Beta Was this translation helpful? Give feedback.
-
|
Tried again in a newly scaffolded Laravel project. Should you reconsider moving this discussion into an issue? |
Beta Was this translation helpful? Give feedback.
-
|
I'm experiencing the same thing and managed to temporarily fix it by including the missing packages in my own "devDependencies": {
"@vue/babel-plugin-jsx": "^1.1.0",
"@vue/compiler-sfc": "^3.2.31",
"axios": "^0.21.2",
"babel-plugin-syntax-jsx": "^6.18.0",
"laravel-mix": "^6.0.41",
"postcss": "^8.3.11",
"resolve-url-loader": "^5.0.0",
"sass": "^1.49.11",
"sass-loader": "^12.6.0",
"vue-loader": "^16.8.3"
},
"dependencies": {
"@inertiajs/inertia": "^0.11.0",
"form-backend-validation": "^2.3.3",
"inflector-js": "^1.0.1",
"vuex": "^4.0.2"
}I also needed to change the Note that in my case the custom nova packages are developed outside of Looking forward to a better solution. 😃 PS: there's a typo in https://nova.laravel.com/docs/4.0/upgrade.html#removal-of-laravel-nova-npm-dependency
|
Beta Was this translation helpful? Give feedback.
-
|
Do you have an example of what you had to do for your laravel-nova alias? I have the following in a component i am working on updating: mix.alias({
'laravel-nova': path.join(__dirname, '../../vendor/laravel/nova/resources/js/mixins/'),
});But doesn't seem to work as i still get the following when compiling: |
Beta Was this translation helpful? Give feedback.
-
|
Your alias seems correct. You probably have to change the import in your component since the alias only provides access to mixins, i.e. At the same time, if you would follow the documentation you would not have access to the Can someone explain the reason for using |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
After following the upgrade guide for Nova 3 to Nova 4 step by step I am still having problems creating custom tools, fields etc.
For example creating a custom field using the following command.
When trying to compile the assets for this field I get the following stack trace:
Not sure if I missed anything from the upgrading steps but everything else works. Never had a problem with custom fields, tools on Nova 3.
Beta Was this translation helpful? Give feedback.
All reactions