Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use ejs.render when options.client is true #96

Open
megakoresh opened this issue Jun 16, 2017 · 4 comments
Open

Don't use ejs.render when options.client is true #96

megakoresh opened this issue Jun 16, 2017 · 4 comments

Comments

@megakoresh
Copy link

Tried to use this to compile clientside templates, but since it uses ejs.render, it will throw an error on various undefined variables during compilation. I can't provide browser variables - the plugin should use ejs.compile if it sees options.client is set to true.

@rogeriopvl
Copy link
Owner

@megakoresh thanks for the feedback!

If you wish to contribute a pull request is very welcome.

Anyway I can fix it, but I can't guarantee when.

megakoresh added a commit to megakoresh/gulp-ejs that referenced this issue Jun 16, 2017
Clientside templates will be named same as source files without extension, optionally adding `settings.suffix` to the end.
Set options.filename to `file.basename` for caching (speeds up gulp watch task when working).
New settings:
`settings.suffix` - when `options.client` is `true`, appends the string provided to the end of the generated clientside template.
Should fix issue rogeriopvl#96
@megakoresh
Copy link
Author

Done.

@megakoresh
Copy link
Author

Hello? Can you merge that thing or say why it can't be merged? I'd really rather avoid linking a fork as dependency for my project.

@iiAbady
Copy link

iiAbady commented Jun 21, 2019

@rogeriopvl fix pls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants