can't resolve CSS file with custom workspace

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Trying to create a project with a custom page template and shared CSS file and getting a build error. (related to #80 )

$ yarn build
yarn run v1.12.3
$ yarn clean && node ./packages/cli/index.js build
$ rimraf ./**/.greenwood/** && rimraf ./**/public/** && rimraf ./coverage
-------------------------------------------------------
Welcome to Greenwood ♻️
-------------------------------------------------------
Reading project config
Initializing project workspace contexts
Generating graph of workspace files...
Scaffolding out project files...
Generate pages from templates...
Writing imports for md...
Writing Lit routes...
setup index page and html
Scaffolding complete.
Building project for production.
Building SPA from compilation...
./.greenwood/about/about.js
Module not found: Error: Can't resolve '../theme.css' in '/Users/owenbuckley/Workspace/project-evergreen/repos/greenwood/.greenwood/about'

Details

Workspace

www/
   pages/
     index.md
     about.md
    templates/ 
      page-template.js
    theme.css

Config

const path = require('path');

module.exports = {
  workspace: path.join(__dirname, 'www'),
  title: 'Greenwood',
  meta: [
    { property: 'og:site', content: 'greenwood' },
    { name: 'twitter:site', content: '@PrjEvergreen' }
  ]
};

Note: I wasn't able to reproduce in the build.default.workspace-template-page-style even after adding a pages/ directory with an index.md and about.md so I think it could be related to using a custom workspace?

[thescientist13]

Confirmed it via spec using just an index.md. So it's definitely related to custom workspace

[thescientist13]

Oh, I think I see the issue.. it's because if it isn't in a directory, the import won't get mapped by webpack.

So instead of

www/
  theme.css

it will work as this though

www/
  styles/
    theme.css

[hutchgrant]

yes it needs to be in a folder to get imported correctly by nodemodulereplacement

[thescientist13]

I think we've covered this through the docs that everything needs to be in a directory. Not sure what the effort is to support this or if it's worth it?

[thescientist13]

I think this is resolved now with #355 , maybe just need to make sure there is a test for this

[thescientist13]

not sure this is an issue anymore in v0.10.0.