Add LightningCAD Generator

[Malachirwin]

Why?

The former system for spinning up a L.CAD app doesn't work in the slightest and was not worth repairing. This pulls some pieces from that but is implemented on rolemodel_rails

What Changed

• Pull required setup from the old generator
• Split the generators into install, test, and webpack
• Add ChromeCAD support out of the box

What the generator adds

• Global setup
  • .npmrc
  • .eslintrc.js
• L.CAD Setup
  • Initializers
    • javascript/config/initializers/smartJSON.js
  • React components
    • javascript/components/LocalIconFactory.jsx
    • javascript/components/MaterialIcon.jsx
• Demo editor
  • controllers/editor_controller.rb
  • views/editor/editor.html.slim
  • javascript/components/App.jsx
• Jasmine test setup
  • jasmine.json
  • spec/javascript/shared/TestSetup.js
  • spec/javascript/shared/testSpec.js

Later

This doesn't fully support the setup for persisted project setup which is most of the use case we need to setup. This only replaces the old generators that don't work. After we have the replacement we can look at some of those other bells and whistles.

[kylesmile]

One thing we'll want to keep in mind is that this repo is public at the moment, whereas LightningCAD is private. We'll want to be mindful of how much L.CAD-specific code ends up in this repo.

[kylesmile]

Probably better to just use the ESLint config provided by the generic (non-L.CAD) generator. There might be changes from projects that could be good to bring in to our base config.

[kylesmile]

I don't think NODE_PATH works with ESM, but we can add a custom import hook to replicate the behavior.

[kylesmile]

We probably don't want to change the output target.

[kylesmile]

I don't think this is needed, since the base config doesn't seem to exclude node_modules from being processed with esbuild-loader.

[OutlawAndy]

@Malachirwin Looks like there is a lot here. Since LightningCAD apps are a thing unto themselves, would it make sense to convert this into a stand alone application template instead? That may be easier to maintain over time & across major Rails versions.

That wouldn't prevent you from making use of generators in the rolemodel_rails gem either. For example:

gem_group :development do
  gem 'rolemodel_rails', github: 'RoleModel/rolemodel_rails'
end

# ...

after_bundle do
  rails_command('generate rolemodel:slim')
  rails_command('generate rolemodel:webpack') if yes?('Use Webpack?')
  rails_command('generate rolemodel:testing:all')
end

cc @kylesmile , @Jeremy-Walton