-
Notifications
You must be signed in to change notification settings - Fork 9
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
Propshaft #89
Merged
Merged
Propshaft #89
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
tricknotes
commented
Aug 21, 2024
•
edited
Loading
edited
- Migrate SCSS to CSS.
- Drop sprockets.
- Drop Node.js and its dependencies.
tricknotes
force-pushed
the
propshaft
branch
2 times, most recently
from
August 21, 2024 16:13
30f6dcc
to
3f9f561
Compare
tricknotes
force-pushed
the
propshaft
branch
2 times, most recently
from
August 22, 2024 13:25
5c503c7
to
3f9f561
Compare
Umm, Gmail doesn't support custom css property. |
Now, we use no any Node.js based compilers.
To support Gmail.
Okay, almost works. |
This PR reduced slug size. --- before.txt 2024-08-23 12:09:52
+++ after.txt 2024-08-23 12:10:40
@@ -7,47 +7,32 @@
-----> Using Ruby version: ruby-3.3.4
-----> Installing dependencies using bundler 2.5.6
Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 bundle install -j4
- Bundle complete! 22 Gemfile dependencies, 99 gems now installed.
+ Bundle complete! 20 Gemfile dependencies, 93 gems now installed.
Gems in the groups 'development' and 'test' were not installed.
Bundled gems are installed into `./vendor/bundle`
- Bundle completed (0.44s)
+ Bundle completed (0.46s)
Cleaning up the bundler cache.
Removing bundler (2.5.6)
-###### WARNING:
- Installing a default version (20.9.0) of Node.js.
- This version is not pinned and can change over time, causing unexpected failures.
-
- Heroku recommends placing the `heroku/nodejs` buildpack in front of
- `heroku/ruby` to install a specific version of node:
-
- https://devcenter.heroku.com/articles/ruby-support#node-js-support
------> Installing node-v20.9.0-linux-x64
-----> Detecting rake tasks
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
To use multipart middleware with Faraday v2.0+, install `faraday-multipart` gem; note: this is used by the ManageGHES client for uploading licenses
- Asset precompilation completed (2.66s)
+ I, [2024-08-22T16:01:45.734498 #284] INFO -- : Writing application-3f50a875.css
+ Asset precompilation completed (2.34s)
Cleaning assets
Running: rake assets:clean
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
To use multipart middleware with Faraday v2.0+, install `faraday-multipart` gem; note: this is used by the ManageGHES client for uploading licenses
+ I, [2024-08-22T16:01:48.010420 #289] INFO -- : Removed application-1a927a8398e21c238ff3e05c201713897dee33e29f5689349aa9f3157a7c309e.css
-----> Detecting rails configuration
-###### WARNING:
- Installing a default version (20.9.0) of Node.js.
- This version is not pinned and can change over time, causing unexpected failures.
-
- Heroku recommends placing the `heroku/nodejs` buildpack in front of
- `heroku/ruby` to install a specific version of node:
-
- https://devcenter.heroku.com/articles/ruby-support#node-js-support
-----> Discovering process types
Procfile declares types -> web
Default types for buildpack -> console, rake
-----> Compressing...
- Done: 77.4M
+ Done: 40.1M
-----> Launching...
- Released v673
+ Released v678
https://starseeker-dev.herokuapp.com/ deployed to Heroku
This app is using the Heroku-22 stack, however a newer stack is available.
To upgrade to Heroku-24, see: Before
After
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.