importmap-rails VS TinyMCE

Importmap audit - “checks the NPM registry for known security issues”

It worked, but JS changes were not coming through. Digging into the Importmap docs (see 'sweeping the cache', it monitors changes according to the setting config.importmap.cache_sweepers. So, by adding the locations where I have my JS files, I also got JS changes passed through.

You can't use TypeScript, or anything that requires pre-compile, with importmap. answered issue

Let's begin by installing the necessary dependencies. The first gem generates the importmap object, manages caching, and helps with library installations, among other things. I recommend reading the entire readme to become familiar with its capabilities. The second gem will be discussed later, it is used to compile JSX files. Gemfile

Yeah, those were brand new right around the time I started this project a few years ago with Rails 7 (or was it 6.1?). I actually ended up removing them in favor of importmap-rails since I wanted as simple of a frontend as possible and I wasn't sure of relying on what was, at the time, a brand new way of doing frontend work. Things change so quickly in JS-land that I'm always hesitant to make something a dependency unless it has a strong track record of being continuously maintained.

source "https://rubygems.org" git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby "3.1.0" # Bundle edge Rails instead: gem "rails", github: "rails/rails", branch: "main" gem "rails", "~> 7.0.4", ">= 7.0.4.2" # The original asset pipeline for Rails [https://github.com/rails/sprockets-rails] gem "sprockets-rails" # Use sqlite3 as the database for Active Record gem "sqlite3", "~> 1.4" # Use the Puma web server [https://github.com/puma/puma] gem "puma", "~> 5.0" # Use JavaScript with ESM import maps [https://github.com/rails/importmap-rails] gem "importmap-rails" # Hotwire's SPA-like page accelerator [https://turbo.hotwired.dev] gem "turbo-rails" # Hotwire's modest JavaScript framework [https://stimulus.hotwired.dev] gem "stimulus-rails" # Build JSON APIs with ease [https://github.com/rails/jbuilder] gem "jbuilder" gem "mongoid" gem "mongoid-grid_fs" gem 'bootstrap', '~> 5.2.2' #sourced from https://github.com/twbs/bootstrap-rubygem gem 'rack-cors' # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem "tzinfo-data", platforms: %i[ mingw mswin x64_mingw jruby ] # Reduces boot times through caching; required in config/boot.rb gem "bootsnap", require: false

Also, installing StimulusReflex seems quite not easy for the moment: It seems there are some quirks along the way if you're using import-maps for managing javascript dependencies as I do. Embracing the Rails way at least prevents you from this sort of issue.

If you're using importmap-rails, you'll need to pin stimulus-multiselect:

While I prefer using importmaps-rails to jsbundling-rails, I found many developers and companies want to have the ability to use JS libraries as they used with Webpack. Old habit I think.

TinyMCE provided a bit more information about this change in a GitHub discussion thread here: https://github.com/tinymce/tinymce/discussions/9496

As I posted there, this directly affects my open source project which is heavily tied to TinyMCE so I may end up forking, and reducing down to what my project needs to reduce maintenance scope & burden.

TinyMCE have been jumping around with their licensing. They were under LGPL, with some (what I believe were) misleading guidance into meeting the LGPL (they specified rules about keeping specific branding elements). They then jumped to MIT, and since moved some of the open plugins to their commercial offering. Now they're making this change.

TinyMCE - rich text editing API. Core features are free for unlimited usage.

Luckily, implementing a basic text editor in your React application is a fairly straightforward process. In this article I will show you how to implement a rich text editor using TinyMCE.

I'm using TinyMCE as the rich text editor, you can replace it with something else, or simply use a if you wish.

Depends on your frontend's stack but the simplest to setup is probably TinyMCE. It's more limited than the other options in terms of customizability and extensibility though.

Yes, the most common being TinyMCE.

TinyMCE

I’ve heard good things about TinyMCE - located at https://www.tiny.cloud

TinyMCE - rich text editing API. Core features free for unlimited usage.