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

Update deps & modernize module #178

Closed
wants to merge 7 commits into from
Closed

Conversation

Zertz
Copy link

@Zertz Zertz commented Jun 28, 2018

  • Convert CoffeeScript to plain old JavaScript
  • Update Autoprefixer
  • Update PostCSS
  • Install Prettier
  • Update tests

@coveralls
Copy link

coveralls commented Jun 28, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 822a283 on classcraft:master into 3451eab on jescalan:master.

@Zertz
Copy link
Author

Zertz commented Jan 9, 2019

@jescalan Anything we can do to move this project forward?

Copy link
Owner

@jescalan jescalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, missed the email for this earlier. Just left some comments. Changes look great, thank you so much for the contribution!

.npmignore Outdated
@@ -1,3 +1,2 @@
test
.editorconfig
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would you delete the editorconfig file?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can leave it if you prefer

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do - editorconfigs are a good way to stay in sync with editor-level settings like indentation etc no matter which text editor you are using. There is an argument to be made for prettier superseding it in this case though, as long as prettier running per-commit is made mandatory.

@@ -0,0 +1,3 @@
{
"editor.formatOnSave": true
}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if personal config files were kept out of the primary source if possible

LICENSE.md Outdated
@@ -1,5 +1,4 @@
License (MIT)
-------------
## License (MIT)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why change this to an h2? It is the primary heading...

"coveralls": "2.13.1",
"css-parse": "2.0.0",
"istanbul": "0.4.5",
"mocha": "3.4.1",
"mocha-lcov-reporter": "1.3.0",
"prettier": "^1.13.7",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prettier is a dep but is not actually used anywhere (other than perhaps your personal vscode settings). If you'd like for the project to use prettier for formatting, it needs to be implemented somehow. Typically I use a "format" npm script set up with a pre-commit hook.

@@ -1,2 +1,2 @@
p
display: flex
display flex
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove the colon here? I prefer using colons even within stylus to make the key/value split clear and the code more understandable.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree on readability, the change was mostly because stylus allows it and to make sure it's correctly transpiled.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This library doesn't need to test stylus' features - the fact that there are no brackets is already enough to separate it from normal css and ensure it is being transpiled 😀

done();
});
});
});
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would prefer to commit a package-lock.json rather than a yarn lock, as npm is the more frequently used option and the default for node.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, it shouldn't actually even be here! Apps should manage their lock file and not libraries, I'll remove it entirely.

@jescalan
Copy link
Owner

Made most of these changes directly - thank you for the contribution!

@jescalan jescalan closed this Jul 26, 2019
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

Successfully merging this pull request may close these issues.

3 participants