-
Notifications
You must be signed in to change notification settings - Fork 12
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
Path normailizing #72
Comments
Great! Looking forward for the patch or pull request |
Hi guys! Any updates about platform independent path normalizer? |
Did the author abandon this cool template engine? |
I was not updating the project because it was pretty stable for me and didnt require any new features. |
@vinhtq I have updated the project (to typescript 1.5 and compatible with Visual Studio Code) so I can start making updates again. I suppose you are getting this problem too. Can you create a small zip file containing a very small project reproducing the problem so I can fix it properly? Thanks in advance. |
@soywiz Sorry for replying so late! Currently i want to use your template engine for my website! It is really cool because i also worked with twig of Symfony. I found your template engine is what i need! But the latest commit was 2 years ago so i want to know whether it is still being developed. Great to hear from you! Thank you for your work! |
I've been trying to use atpl.js with gulp-consolidate for a static website generation project and keep running in to the issue that the paths are not properly resolved (I'm running on windows). When I took a peek in the code I saw the path separators are hard coded ('/') and there is a custom rolled normalize method. I think this could be the cause of my problem and I'm writing a patch that will use path.sep and the path.resolve methods provided by the Path package in node.
The text was updated successfully, but these errors were encountered: