-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
An extra ‘viewport’ meta with default template 'src/index.ejs' #1387
Comments
Oh you are right what would be the best solution for that? |
First of all, I think the result should be exactly the same whether you explicitly specify template as src/index.ejs or implicitly use src/index.ejs as fallback when no template is configured. |
Yes that sounds just right |
Bumping as this is still an issue. Agree that this should offer the same behaviour as an explicitly provided user template. |
Oh sorry I forgot about this one! 😱 |
So the problem is here in Lines 76 to 83 in 2f5de7a
The simplest (but pretty dirty) solution would be to check for the existence of a file: if (!userOptions.template && !fs.existsSync('./src/index.ejs') && options.templateContent === false && options.meta) { @jantimon Any other ideas? |
Take into account `src/index.ejs` existence while deciding to add default meta-tags. Closes: jantimon#1387
Added the proposed (but slightly modified) solution as PR #1693 |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Bump to avoid being auto-closed (issue is still unresolved as of v5.5.0) |
Take into account `src/index.ejs` existence while deciding to add default meta-tags. Closes: jantimon#1387
<title>title</title> |
I have an html template file src/index.ejs and the viewport meta has been defined.
When I don't configure the template option (the documentation says that src/index.ejs will be used by default)
Another viewport meta is generated.
But if I specify src/index.ejs as the template
The result is what I expected.
The text was updated successfully, but these errors were encountered: