fix for package generation with uninstalled new packages

[alexcjohnson]

Small fix needed to get dash-component-boilerplate working for totally fresh new packages. Also simplified import_module syntax. This branch is linked to plotly/dash-component-boilerplate#75 - ideally we'll make a new release before we merge that.

Yet another reason to move js_dist and css_dist into the YAML file - then we can stop importing the package we're in the middle of creating 😅

[rpkyle]

💃

[rpkyle]

Learned something new today; hadn't used this method previously.

[rpkyle]

Yet another reason to move js_dist and css_dist into the YAML file - then we can stop importing the package we're in the middle of creating 😅

(on the 🚇, so have a little "extra" time)

I was chatting with @Marc-Andre-Rivet about this, and the YAML metadata migration project got me thinking about what would be (from my perspective) an ideal package generator:

• building a new library for (current or future) backends should not require us to significantly refactor/rewrite package generating functions
• component developers should not need to write code to build packages, just need to modify a second, backend-specific YAML file and insert elements corresponding to features to generate, based on templates
• the system should be essentially modular and relatively easy for third-party developers to understand

Perhaps something like ...

backend: "R"
        requirements:
            DESCRIPTION: <path-to-description-file-template>
            NAMESPACE: <path-to-namespace-file-template>
            R: <path-to-component-file-template-directory>