Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when trying to run project #87

Closed
lucaslevin opened this issue Jan 14, 2021 · 5 comments · Fixed by #94
Closed

Error when trying to run project #87

lucaslevin opened this issue Jan 14, 2021 · 5 comments · Fixed by #94
Assignees
Labels
bug Something isn't working
Milestone

Comments

@lucaslevin
Copy link

My steps:

  • npm init microsite microsite
  • cd /microsite
  • yarn install
  • yarn start

➜ microsite yarn start
yarn run v1.22.10
warning ../../package.json: No license field
$ microsite
file:///##/##/##/microsite/node_modules/microsite/dist/cli/microsite-dev.js:53
const [errs, config] = await loadConfiguration('dev');
^

TypeError: (intermediate value) is not iterable
at dev (file:///##/##/##/microsite/node_modules/microsite/dist/cli/microsite-dev.js:53:28)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@AndiLavera
Copy link

Just downloaded, ran init and then tried starting the dev server. This was the result:

(node:251078) UnhandledPromiseRejectionWarning: TypeError: (intermediate value) is not iterable
    at dev (file:///home/andrew/.nvm/versions/node/v14.15.3/lib/node_modules/microsite/dist/cli/microsite-dev.js:54:28)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:251078) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:251078) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@nilskjQL
Copy link

Did the same thing as above, same error with both node v12.9.1 and v14.15.4

yarn run v1.22.5
$ microsite
(node:20267) UnhandledPromiseRejectionWarning: TypeError: (intermediate value) is not iterable
    at dev (file:///Users/nilskjellman/xxx/xxx/microjazz/node_modules/microsite/dist/cli/microsite-dev.js:53:28)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:20267) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:20267) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✨  Done in 0.65s.
nilskjellman@Nilss-MBP-2 microjazz % node --version
v14.15.4```

@KoharaKazuya
Copy link

microsite depends on snowpack@^3.0.0-rc.2 and resolves snowpack@3.0.10 at the moment.
Snowpack changed createConfiguration API.

@natemoo-re
Copy link
Owner

Sorry about this, everybody!

As a silly workaround yarn users could add the following to their package.json.

  "resolutions": {
    "microsite/snowpack": "3.0.0-rc.2"
  }

There are a few things happening here:

  • I should have pinned the dependency to snowpack@3.0.0-rc.2 exactly (for multiple reasons.) It was probably not a great idea to depend on an rc anyway.
  • There were a number of breaking changes with snowpack@3.0.0 that didn't make it into an rc ahead of time. Some pretty straightforward but others were more subtle. Without the advance warning, those caught me off guard.
  • I merged 1.1.0-next into Microsite's main branch, so that blocked me from putting a quick patch out. Lesson learned!

Hoping to get v1.1.0 out the door very soon. Feel free to follow #94.

@natemoo-re natemoo-re added the bug Something isn't working label Jan 21, 2021
@natemoo-re natemoo-re self-assigned this Jan 21, 2021
@natemoo-re natemoo-re linked a pull request Jan 21, 2021 that will close this issue
2 tasks
@natemoo-re
Copy link
Owner

Sorry for the frustration, everybody! You should now be able to manually install microsite@next with any package manager to fix this (and yarn users can remove the resolutions workaround.)

microsite@1.1.0 is still waiting on snowpack@3.0.12, but unfortunately there hasn't been a Snowpack release for about a month. As soon as that drops, Microsite is ready to go out the door.

@natemoo-re natemoo-re pinned this issue Feb 21, 2021
@natemoo-re natemoo-re unpinned this issue Mar 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants