How to exclude css modules from being bundled in js?

[akaSybe]

Is there some flag to disable bundling css-modules into js-bundle?

[aminya]

I have the same problem. I have a library that imports CSS into the components. I do this so Parcel transforms and bundles CSS for me. But I don't want them to be required into the JS bundle which breaks the workflow of anyone who does not use Parcel or similar bundlers.

https://github.com/aminya/solid-simple-table/blob/20c4c543fe4604acd3877426055abc474416d67a/src/SimpleTable.tsx#L2

[chisholmd]

I will give that a try. But excluding a file using "includeNodeModules" is a little unintuitive lol

[chisholmd]

I expect I am being thick headed about this but... if my source has an import statement like:
import * as clientConfig from '/config/client_config.js'

and I want that file to still be imported as a separate file after bundling...
"alias": {
"my-config-module": { "fileName": "./config/client_config.js" }
}
Is that all I have to do?

[chisholmd]

I think maybe I need to use some sort of dynamic import instead

[chisholmd]

I realize that I am also leaving out a critical part of the requirement. Currently I am using successive imports to override previous values in my initial state

initialState.js
        import * as defaults from '/config/defaults.js'
        import * as clientConfig from '/config/client_config.js'
        import * as userConfig from '/config/user_config.js'
        
        export default {
            ...defaults.default,
            ...clientConfig.default,
            ...userConfig.default
        }

Where \config\defaults.js might have:
Idle_timeout: 90

But \config\clientConfig.js might have:
Idle_timeout: 30

Because of the order of import, the client configs only need to create entries for values they want changed from the default.

And the file has to be unbundled so that local administrators can easily find and edit them. So they need to be not bundled, and loaded in a specific order.

The moer I look at this the more dynamic import seems to make sense,

[chisholmd]

Damn. I thought it was looking good to have a config loader run when the app init's to dynamically import modules....

  import('../config/user_config.js').then((userConfig) => {
            Object.keys(userConfig.default).forEach(function(key) {
                storeInstance.dispatch("setState", {property: key , value: userConfig.default[key] } )
            });
        })

...but no, it looks like parcel read this and bundled them anyway.