[webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.
- options has an unknown property 'publicPath'. These properties are valid:
object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, setupExitSignals?, static?, watchFiles?, webSocketServer? }
Also
npm start build
produces warning: clean-webpack-plugin: options.output.path not defined. Plugin disabled
$ npm install --save-dev typescript webpack ts-loader webpack-cli
npm WARN @babylonjs/inspector@4.2.0 requires a peer of @types/react@>=16.7.3 but none is installed. You must install peer dependencies yourself.
npm WARN @babylonjs/inspector@4.2.0 requires a peer of @types/react-dom@>=16.0.9 but none is installed. You must install peer dependencies yourself.
npm WARN bjs-temp@1.0.0 No description
npm WARN bjs-temp@1.0.0 No repository field.
npm ERR! code EPERM
npm ERR! syscall rename
npm ERR! path C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json.3938245996
npm ERR! dest C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json.3938245996' -> 'C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json'
npm ERR! [OperationalError: EPERM: operation not permitted, rename 'C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json.3938245996' -> 'C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json'] {
npm ERR! cause: [Error: EPERM: operation not permitted, rename 'C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json.3938245996' -> 'C:\Users\johnk\Documents\BJS TEMP\node_modules\fast-deep-equal\package.json'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'rename',
npm ERR! path: 'C:\\Users\\johnk\\Documents\\BJS TEMP\\node_modules\\fast-deep-equal\\package.json.3938245996',
npm ERR! dest: 'C:\\Users\\johnk\\Documents\\BJS TEMP\\node_modules\\fast-deep-equal\\package.json'
npm ERR! },
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'rename',
npm ERR! path: 'C:\\Users\\johnk\\Documents\\BJS TEMP\\node_modules\\fast-deep-equal\\package.json.3938245996',
npm ERR! dest: 'C:\\Users\\johnk\\Documents\\BJS TEMP\\node_modules\\fast-deep-equal\\package.json',
npm ERR! parent: 'BJS TEMP'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\johnk\AppData\Roaming\npm-cache\_logs\2021-10-09T09_00_28_105Z-debug.log
w000t this is really strangeā¦ It looks like you are not using the same version of webpack cli / dev server as we do ā¦ which is weird considering we have a lock file
The command should probably be ānpm installā without the names of the dependencies, as we have the dependencies in package.json.
Can I ask both of you if you see a got change in your package.json? Was the webpack version updated?
and making sure that the newly created file was webpack.config.js was closed
everything seemed to install OK.
As did @Todilo when I got to npm run build I got the error message
clean-webpack-plugin: options.output.path not defined. Plugin disabled...
and on
npm run start
clean-webpack-plugin: options.output.path not defined. Plugin disabled...
[webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.
Perhaps someone who knows more of what they are doing could start with a blank root folder and follow the instructions step by step to see if they have the same problem.
I wonder if you could be using webpack 5 somehow (you should double check you have webpack only in the root folder node_modules installed and not in tools/gulp)
Sorry didnāt get any notifications(my fault). I actually though this was guide getting started Babylon when I started. I just wanted to run it outside the online or the IDE (so directly from VSCode) and found this instructions.
It does seem to install webpack 5 which doesnāt seem to be what the author has written the guide for. The syntax of the webserver part has been changed which is unfortunate since googling āGetting started babylonjsā will render that link as a top suggestion.
Is there a getting started local development?
My goal is not to make a game but dabbling with a medical application, hopefully BabylonJS is the tool for me.
Wait, what was the fix for this? Iām new to webpack and everything has been working well with ThreeJS. Thought Iād give Babylon a go and canāt get past installation.
I also get:
āInvalid options object. Dev Server has been initialized using an options object that does not match the API schema.ā when running ānpm run startā
