[Feature Request] Option to set allowed extensions

[EricKotato]

Allowed extension list is hardcoded, so it can cause troubles. Mine, for example, that couldn't include local CSS file.

[ChrisKnott]

@RadRussianRus the allowed extensions is only for looking for functions that have been exposed, it should still serve .css

[EricKotato]

It's strange because local .css wasn't working for me until I commented out this.

[brumar]

This is still a relevant feature request to my eyes :)
I had to manually edit the allowed extensions to make eel work with my transcrypt files (ending up with .py). Something like that would been neat:

eel.search_in(extensions=[".js", ".html"], folders="./web", recursive=True)

[ChrisKnott]

@brumar sorry for not replying to several good points you've made.

I should have some time soon to work on Eel and I will incorporate this change.

I am hoping to release 1.0 over the Christmas period

[brumar]

@ChrisKnott Great ! As you noticed, I am very motivated by this project. I just pushed the repository where I am playing with Transcrypt and Eel : https://github.com/brumar/tranquille. As I wrote in the README I believe Transcrypt is a very good partner to Eel. Let me know if you have an idea of you would like that I contribute. Maybe some tests should be introduced ? Sorry, this is off-subject concerning the issue :)

[KyleKing]

Setting the searchIn option would also be really useful for me for typescript files

For example, this is how I handle development/production builds from within the Create-React-App (snippet based on: AnthoniG/eel_react) where an additional option, 'searchIn': ['.tsx', '.ts', '.js', '.html'], would be available:

def start_eel(develop=True):
    if develop:
        eel.init('src')
        page = {'port': 3000}
        flags = ['--start-fullscreen', '--auto-open-devtools-for-tabs']
    else:
        eel.init('build')
        page = 'index.html'
        flags = ['--start-fullscreen']

    eel.start(page, options={
        'searchIn': ['.tsx', '.ts', '.js', '.html'],  # ** Proposed Option **
        'mode': 'chrome-app',
        'port': 8080,
        'host': 'localhost',
        'chromeFlags': flags
    })

Also, I think it would be useful to add some clarification to the README that eel uses a regular expression eel.expose\((.*)\) to locate the exposed functions. This tripped me up for a few minutes