Closed rosskevin closed 4 weeks ago
I have now the ownership of the extension so I should be able to update the version "soon". But my time is really limited for MJML so I do my best to handle support + continue dev on those projects.
Thank you @iRyusa
I don't know vscode extensions, but I'll take a swing at updates and see if I can get you a PR that moves this forward a little.
It looks like this needs a vscode
migration that is old enough, I had to use the wayback machine to find it!
http://web.archive.org/web/20210505205913/https://code.visualstudio.com/api/working-with-extensions/testing-extension#migrating-from-vscode
I'll see if I can get updates working.
PR pushed, changes were reasonably straightforward, but it needs reviewed due to may lack of experience in this area.
Now I'll see if I can run it!
Should be good now 👍
Before you open an issue, please check if a similar issue already exists or has been closed before.
Expected behavior
I expect to be able to build this from source. No new tags, no new releases are listed on the repo page, but there were merges of PR's such as #47 which is what I need
Actual behavior
And checking the dependencies - they are very far out of date:
Steps to reproduce the problem
Screenshot / GIF
Please attach screenshot/gif if you consider them as helpful to understand/reproduce the issue.
Specifications
master
0ffe95568452713f3f9ae70c4465b5344f7fd560
Other information
I'm confused, a recently merged PR, very old tags, very old releases, VERY old dependencies. There was a mention in #47 about a release this week, but there are no other branches....confused.