You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initialising a new project with npm init @open-wc sets up a project that doesn't work.
When running yarn install, one gets warned that two packages are missing:
@babel/core, required by @rollup/plugin-babel and @babel/preset-env
esbuild, required by rollup-plugin-esbuild
Then yarn run lint and yarn run format have missing packages as well, and one has to run the commands repeatedly to figure out the next package they should install:
eslint-plugin-wc
eslint-plugin-lit-a11y
eslint-plugin-lit
eslint-plugin-html
eslint-plugin-no-only-tests
eslint-plugin-import
@babel/plugin-syntax-import-assertions
yarn run test requires @web/test-runner-playwright and playwright which are of course missing. Besides, the template seems to create a web-test-runner.config.js and a web-test-runner.config.mjs, though only one is needed. Perhaps one should be warned that web-test-runner.config.mjs takes priority and updating web-test-runner.config.js while keeping around the other has no effect. On another note, the imports in the config file are commented out for some reason.
yarn run analyze doesn't work: sh: cem: command not found. Only God knows what cem is! I suppose it has to do with @custom-elements-manifest/analyzer, which exists as a dependency, but somehow doesn't provide a cem command. And because yarn run build and some other coomands also run analyze, they fail too.
yarn run storybook doesn't work either, even if you drop the analyze part: a prismjs package is missing, and two required files don't exist, .storybook/server.mjs and .storybook/main.js respectively. I initialised them using the sample code at https://modern-web.dev/guides/dev-server/storybook/ and I got yet another error:
Error: require() of ES Module .../.storybook/main.js from .../node_modules/@web/dev-server-storybook/dist/shared/config/readStorybookConfig.js not supported.
I've no idea what that means and at this time I'm too tired to look it up on the Internet.
Are there any plans to making it work?
The text was updated successfully, but these errors were encountered:
Initialising a new project with
npm init @open-wc
sets up a project that doesn't work.When running
yarn install
, one gets warned that two packages are missing:@babel/core
, required by@rollup/plugin-babel
and@babel/preset-env
esbuild
, required byrollup-plugin-esbuild
Then
yarn run lint
andyarn run format
have missing packages as well, and one has to run the commands repeatedly to figure out the next package they should install:eslint-plugin-wc
eslint-plugin-lit-a11y
eslint-plugin-lit
eslint-plugin-html
eslint-plugin-no-only-tests
eslint-plugin-import
@babel/plugin-syntax-import-assertions
yarn run test
requires@web/test-runner-playwright
andplaywright
which are of course missing. Besides, the template seems to create aweb-test-runner.config.js
and aweb-test-runner.config.mjs
, though only one is needed. Perhaps one should be warned thatweb-test-runner.config.mjs
takes priority and updatingweb-test-runner.config.js
while keeping around the other has no effect. On another note, the imports in the config file are commented out for some reason.yarn run analyze
doesn't work:sh: cem: command not found
. Only God knows whatcem
is! I suppose it has to do with@custom-elements-manifest/analyzer
, which exists as a dependency, but somehow doesn't provide acem
command. And becauseyarn run build
and some other coomands also runanalyze
, they fail too.yarn run storybook
doesn't work either, even if you drop theanalyze
part: aprismjs
package is missing, and two required files don't exist,.storybook/server.mjs
and.storybook/main.js
respectively. I initialised them using the sample code at https://modern-web.dev/guides/dev-server/storybook/ and I got yet another error:I've no idea what that means and at this time I'm too tired to look it up on the Internet.
Are there any plans to making it work?
The text was updated successfully, but these errors were encountered: