Actually, all the new components I have added to my project do fail, and this since I decided to use the all: ‘auto’ import option. The previous list of components that I had listed in config still work, although I did remove them from config.
This is usually a result of a minuscule typo.
For instance, if you are importing your modules like import Vue from ‘vue’, import Vuex from ‘vuex’.
Go through your files and check where you used from ‘Vue’ or from ‘Vuex’ - make sure to use the exact same capitals (uppercase letters) as in your import statements.
The error descriptions should have been written more clearly, but what I explained has been the cause of my problem each time for this error on webpack commands.
I could rename the boot file successfully with this approach, albeit through brute force though.
HOWEVER, the initial warning remains. It must not be related to the boot mainInit file. I will post a different thread as this is not related to the boot file renaming issue.
ps: the warning now:
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
Used by 1 module(s), i. e.
Used by 158 module(s), i. e.