This plugin is deprecated and archived
mrmlnc opened this issue · 10 comments
The main package (stylefmt) that uses this extension is no longer being developed. I don't see the point in using outdated technology.
Instead of stylefmt you can use the following solutions:
I am releasing the last release of this extension and archiving it.
I am ready to back to the plugin support if the main package find a maintainer and back to the active development. Right now, this is the last release (not a latest).
Stylefmt is better than prettier and others which force some styling preferences so I will keep using it. This PR with these updates fixes this plugin even though the main package is no longer developed. It uses my fork of stylefmt that has been updated to fixed packages.
The funny thing is, practically stylefmt works perfectly fine as long as stylelint is kept up to date once or twice a year, because there will be some slight changes in stylelint rule sets that will be outdated in some points. Very small things but affect everyone because packages are not updated. See my other related issues: here, here, here and here.
So basically it means that stylefmt depends on packages like stylelint and it's broken ONLY because the developer is too lazy to run npm update... the stylefmt itself is functioning as long as you update the packages. The maintainer has not updated stylelint for years as seen here, the newest version is 13.6.1. The world we live in...
So for future refrence and other people (you might want to add this to README @mrmlnc if you are not interested in upkeeping this repository any more nor merging my PR) to get vscode-stylefmt working again:
cd ~/.vscode/extensions/mrmlnc.vscode-stylefmt-2.6.1code package.json- Edit lines shown here and save package.json
- Run
npm update - Restart VSCode / Reload extensions from disk
Tested and confirmed working with latest and clean vscode-stylefmt.
JFYI: I can transfer this repository to you. In this case, you will need to publish the extension in the store under your publisher. Alternatively, you can add your changes to the root repository (stylefmt) or become its maintainer.
I don't really have any other VSCode plugins so the world is unfamiliar to me. If you mean this stylefmt repository, its maintainer morishitter has been in the dark for two years and that's the origin of most issues so that won't help. I use stylefmt daily so would be glad to take over. I just need some time to create my own version of the plugin, you can then point this one to the new one. I'll let you know when I have time, may take a while though.
Hey @mrmlnc, I now have my active fork as a working VSCode plugin:
@mrmlnc Do you have an idea why it says
Activating extension 'ronilaukkarinen.vscode-stylefmt' failed: Cannot find module 'postcss'
Require stack:
- /Users/rolle/.vscode/extensions/ronilaukkarinen.vscode-stylefmt-2.7.6/out/stylefmt/index.js
- /Users/rolle/.vscode/extensions/ronilaukkarinen.vscode-stylefmt-2.7.6/out/extension.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js.
Everything should be all right and I haven't done any modifications other than installed travis and updated dependencies... 🤔 I'm kinda new to this as this is my first vscode plugin.
On development mode F5 it works though...
Loading development extension at /Users/rolle/Projects/vscode-stylefmt
Why is that?
...well, I had node_modules inside .vscodeignore... Thank goodness it works now. (ref)
@mrmlnc As a reminder, I have active repos for both vscode-stylefmt and stylefmt, you could point your users to this direction. Thanks.
A link to your extension has been added to the plugin description.