发表新帖
发表新帖

Chrome's map to file system resource not working after update

后端 未结
关注
11 2111
野的像风
野的像风 2021-02-02 07:41

I can add a folder to the workspace (which doesn\'t seem to do anything, as far as I can tell), but the \"map to file system resource\" option seems to have been removed, and I

相关标签:
11条回答
  • 别那么骄傲
    2021-02-02 08:17

    The "Map to File System Resource..." menu item is missing. There appears to be no way to map files. It is completely broken as far as I can tell.

    0 讨论(0)
  • 没有蜡笔的小新
    2021-02-02 08:18

    I've just fiddled around with a problem, where only some files got mapped to my local workspace.

    Turned out that Google Chrome also checks and compares the last modified date of your files.
    If the file on the server has a more recent date than your local copy, this file won't be mapped.

    I deleted the Bootstrap file on the server side and uploaded my local copy, which has an older last modified date. Google Chrome instantly mapped the file to my local workspace.
    Out of curiosity I ran touch bootstrap.min.js on my server to set the last modified date to today. This broke my file mapping again.

    0 讨论(0)
  • 梦谈多话
    2021-02-02 08:21

    I had the same problem so I downgraded to Chrome 62 (preferences, history, extensions and so on are preserved).

    1. Download Chrome 62 from
      https://www.slimjet.com/chrome/google-chrome-old-version.php .
    2. On OS X trash /Applications/Google Chrome.
    3. Switch off auto-update by setting "defaults write com.google.Keystone.Agent alwaysPromptForUpdates 1". Default is 0.
    4. May be you have to set "defaults write com.google.Keystone.Agent checkInterval 0" too. Default is 18000.
    5. Install Chrome 62 as usual.

    After starting Chrome 62 open "About Google Chrome". Chrome is checking for updates, but will prompt you to confirm.

    0 讨论(0)
  • Happy的楠姐
    2021-02-02 08:21

    For me, the problem turned out to be the presence of the copyright symbol © in the file headers (which affected just about every file). With this character in the files, devtool refused to map the files but with it removed, the files map fine.

    0 讨论(0)
  • 耶瑟儿～
    2021-02-02 08:21

    Had the same problem, but when my source maps included sourcesContent, the file mappings were automatically made and I could live edit my scss. Apparently chrome uses the content to find the right file.

    node-sass --source-map-contents

    0 讨论(0)
 看不清?
提交回复
热议问题