Wednesday, December 27, 2023
HomeApplemigration - Migrating from Intel Macbook Professional to M3 Max causes points...

migration – Migrating from Intel Macbook Professional to M3 Max causes points with debugging frontend Vue purposes


Just lately I bought a brand new Macbook Professional (M3 Max) and used the Migration Assistant to primarily clone the prevailing Macbook Professional (Intel chip) I used to be utilizing beforehand.

How I stumbled upon asking this query on Ask Completely different. If this belongs elsewhere, please let me know.

If I create a model new Vue2 mission on my outdated machine utilizing Vue CLI like this: vue create sample-project and I throw a debugger within the created hook of the HelloWorld.vue part that’s routinely generated and I run the mission and open dev instruments in any browser (Chrome, Safari, and many others.) then the result’s that I’ll hit that debugger breakpoint within the created hook and see it like this in dev instruments:
Image of debugger breakpoint being hit in Chrome dev tools

Nevertheless, if I attempt to do the identical on my new machine I don’t get the identical end result, the supply maps appear tousled if I attempt to open the identical HelloWorld.vue file in dev instruments. On my new machine it seems to be like this:
Image of broken source maps or unknown bug causing Vue files to show up odd in Chrome dev tools

If I compress the mission from my outdated machine and ship it to my new machine and check out working it with out a lot as doing something to it in any respect I can not hit the identical break level. Moreover if I do the reverse and create a brand new mission on my new machine after which ship it again to the outdated one, issues don’t work on the brand new one however will nonetheless work on the outdated machine and my work machine.

Sanity checks I’ve achieved:

  • node variations are similar (18.14.2)
  • Vue CLI variations are similar (@vue/cli 5.0.8)
  • What else ought to I be contemplating?

Issues I’ve tried:

  • Restarting my machine.
  • Doing a contemporary set up of Vue CLI utilizing –force
  • Doing a contemporary set up of node
  • Restarting a number of extra instances after attempting different issues to no avail

Nothing has labored. As one other sanity verify I despatched that very same zipped up HelloWorld mission to my work machine the place I’ve by no means ran a vue mission and it runs and debugs simply high quality there as nicely.

Variations I’ve observed?
If I open the supply/check (my mission identify) I see these variations within the recordsdata:
New machine:
Picture from Chrome dev tools sources tab showing missing files on the new machine compared to the old one

Outdated machine:
Picture from Chrome dev tools sources tab showing complete set of files from a new project as we would expect

Any concepts why that is occurring solely on this machine and what I can attempt to repair it?



Supply hyperlink

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments