UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.28 Safari/537.36

Steps to reproduce the problem:
1. Extract the attached archive into a directory
2. Create a directory that contains symlinks to the extracted files:

cd extracted-files
mkdir links
ln -s `readlink -f *` links

3. Load the directory that contains the symlinks as an unpacked extension

What is the expected behavior?
Both by-manifest.js and by-script.js should be executed in the tab the extension opens.

Paths pointing to symlinks in extension manifests (like icons and content_scripts paths) should be resolved by following the symlink just like paths to tabs.executeScript and resource requests.

What went wrong?
Unexpected behaviour (see above)

WebStore page: 

Did this work before? N/A 

Chrome version: 55.0.2883.28  Channel: beta
OS Version: 4.8.13-1-ARCH
Flash Version: Shockwave Flash 24.0 r0

Symlinks are very useful in build processes because you can have a destination directory with static files that update instantly.