area17 / blast

Storybook for Laravel Blade 🚀

Home Page:https://dev.to/area17/getting-started-with-blast-storybook-for-laravel-blade-c5c

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

blast:launch fails on fresh install 1.6

csrui opened this issue · comments

Running the blast:launch command doesn't produce the expected result which would be to access either localhost:6006 or freshl9.test/storybook_preview and see StoryBook.

Blast: 1.6
Laravel: 9.9.0
PHP: 8.1.4
Node: 17.8.0

Also to node, the process keeps running until I ^C which you can notice in the log below.

Here's the console output.

[0] info @storybook/server v6.4.9
[0] info 
[0] (node:63163) DeprecationWarning: --static-dir CLI flag is deprecated, see:
[0] 
[0] https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#deprecated---static-dir-cli-flag
[0] (Use `node --trace-deprecation ...` to show where the warning was created)
[0] info => Loading presets
[0] info => Serving static files from /freshl9/public at /
[0] info => Loading custom manager config
[0] info => Using PostCSS preset with postcss@7.0.36
[0] info => Using default Webpack5 setup
[0] info => Loading custom manager config
[0] <i> [webpack-dev-middleware] wait until bundle finished
[0] <i> [webpack-dev-middleware] wait until bundle finished
[0] node:internal/crypto/hash:67
[0]   this[kHandle] = new _Hash(algorithm, xofLen);
[0]                   ^
[0] 
[0] Error: error:0308010C:digital envelope routines::unsupported
[0]     at new Hash (node:internal/crypto/hash:67:19)
[0]     at Object.createHash (node:crypto:135:10)
[0]     at BulkUpdateDecorator.hashFactory (/freshl9/vendor/area17/blast/node_modules/webpack/lib/util/createHash.js:145:18)
[0]     at BulkUpdateDecorator.update (/freshl9/vendor/area17/blast/node_modules/webpack/lib/util/createHash.js:46:50)
[0]     at OriginalSource.updateHash (/freshl9/vendor/area17/blast/node_modules/webpack/node_modules/webpack-sources/lib/OriginalSource.js:131:8)
[0]     at NormalModule._initBuildHash (/freshl9/vendor/area17/blast/node_modules/webpack/lib/NormalModule.js:888:17)
[0]     at handleParseResult (/freshl9/vendor/area17/blast/node_modules/webpack/lib/NormalModule.js:954:10)
[0]     at /freshl9/vendor/area17/blast/node_modules/webpack/lib/NormalModule.js:1048:4
[0]     at processResult (/freshl9/vendor/area17/blast/node_modules/webpack/lib/NormalModule.js:763:11)
[0]     at /freshl9/vendor/area17/blast/node_modules/webpack/lib/NormalModule.js:827:5
[0]     at /freshl9/vendor/area17/blast/node_modules/loader-runner/lib/LoaderRunner.js:406:3
[0]     at iterateNormalLoaders (/freshl9/vendor/area17/blast/node_modules/loader-runner/lib/LoaderRunner.js:232:10)
[0]     at /freshl9/vendor/area17/blast/node_modules/loader-runner/lib/LoaderRunner.js:223:4
[0]     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
[0]   opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
[0]   library: 'digital envelope routines',
[0]   reason: 'unsupported',
[0]   code: 'ERR_OSSL_EVP_UNSUPPORTED'
[0] }
[0] 
[0] Node.js v17.8.0
[0] start-storybook --quiet -s /freshl9/public -p 6006 exited with code 1
^C
[2] npm run watch-data exited with code SIGINT                                                                                                                                                                                                                          
[1] npm run watch-components exited with code SIGINT

Although accessing localhost:6006 has no response, accessing freshl9.test/storybook_preview throws a an exception.

Too few arguments to function A17\Blast\Controllers\StoryController::__invoke(), 1 passed in /Users/rui.sardinha/dev/sites/freshl9/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php on line 48 and exactly 2 expected

Let me know if I can provide more context.

As a follow up, I've figured that the issue resides with nodejs 17. Using nodejs 16, the launch command works as intended.

Hi @csrui, thanks for identifying this! We'll take a look at Node.js 17 support.

similar problem with nodejs 20